Closed stijnherreman closed 4 months ago
This is definitely an oversight in the way I implemented some of the DOM methods. This would be easy to fix, the only problem is that it would break binary compatibility, see: http://stackoverflow.com/questions/1456785/a-definite-guide-to-api-breaking-changes-in-net
There are a lot of other changes I would like to make to the DOM model that I've held off on for this reason. I'd planned to have all this be part of 2.0 which would also be created as a cross-platform library. This could be a while off though.
I'm thinking the way to go is to start a pre-2.0 branch in which I can start making API changes like this in the meantime without breaking things for existing users, which I will put out of nuget as a prereleases.
That's a quick response :) I'll be looking forward to future releases.
I might open pull requests in the future, but I've only started working with CsQuery today so I'm still figuring out the basics.
By all means! I welcome any and all contributions, it's a big project.
Are there any plans to support a fluent API for DomElement (and similar classes)?
Instead of
I'd like to write