Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

open up the TemplateFile API in Paket.Core #1201

Closed
krgn opened this issue Nov 8, 2015 · 1 comment
Closed

open up the TemplateFile API in Paket.Core #1201

krgn opened this issue Nov 8, 2015 · 1 comment

Comments

@krgn
Copy link
Contributor

krgn commented Nov 8, 2015

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

@forki
Copy link
Member

forki commented Nov 8, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants