Closed binarycow closed 4 years ago
Hello @binarycow,
I think that in this case option 2 would be easiest.
Updating the version from the NuGet to 1.1.0
would make sense.
And adding an extra class comment on all classes like:
/// <summary>
/// This class is used by XPath.Net internally. It isn't intended for use in application code.
/// </summary>
public abstract class AbstractNode : IEnumerable<AbstractNode>
@binarycow Do you want to create a PR for this?
Sure, I'll submit a PR
Hello! I would like to use your library in my application, but I have a requirement to access the AST. I was hoping you could help.
I can think of three options...
public
- this will expose them for everyone.XPath2
assembly into a shared project. I'd use git subtree to include your repo in my main project repo. I'd reference the shared project, and it would bring your code into my assembly. This lets me accessinternal
types, without exposing them to all consumers of the assembly (as option #2 would do)