You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would be great to be able to re-use the TemplateFile parser code in a project I'm building (https://github.com/krgn/Paket2Nix) but its currently internal/private.
Would you consider making the API public for use in cases where external tools (in this case my tool which reads .lock files to create nix derivations from) need access to this metadata without necessarily having access to the assemblies themselves?
Or, which other process would be recommended in this case?
Reading the assemblies themselves would mean the project would have to be built when my tool is invoked on a project, which might not always be the case.
Thanks!
Karsten
The text was updated successfully, but these errors were encountered:
Sure. Please add methods to PublicAPI.fs - we try to keep that interface
stable.
On Nov 8, 2015 12:38, "Karsten Gebbert" [email protected] wrote:
I would be great to be able to re-use the TemplateFile parser code in a
project I'm building (https://github.com/krgn/Paket2Nix) but its
currently internal/private.
Would you consider making the API public for use in cases where external
tools (in this case my tool which reads .lock files to create nix
derivations from) need access to this metadata without necessarily having
access to the assemblies themselves?
Or, which other process would be recommended in this case?
Reading the assemblies themselves would mean the project would have to be
built when my tool is invoked on a project, which might not always be the
case.
Thanks!
Karsten
—
Reply to this email directly or view it on GitHub #1201.
I would be great to be able to re-use the TemplateFile parser code in a project I'm building (https://github.com/krgn/Paket2Nix) but its currently internal/private.
Would you consider making the API public for use in cases where external tools (in this case my tool which reads
.lock
files to createnix
derivations from) need access to this metadata without necessarily having access to the assemblies themselves?Or, which other process would be recommended in this case?
Reading the assemblies themselves would mean the project would have to be built when my tool is invoked on a project, which might not always be the case.
Thanks!
Karsten
The text was updated successfully, but these errors were encountered: