-
Notifications
You must be signed in to change notification settings - Fork 41
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
Can toJson() functionality be included as well? #1801
Comments
Hey @thosakwe I think I avoided There is quite a bit of special handling of dependencies, for instance. If you want to take a shot, I'd accept a PR, though! |
@kevmoo could I work on this issue? |
Sure! Just make sure you put in plenty of tests. I want to see that at round trips cleanly, etc. |
Is this being worked on? (cc: @AliAkberAakash , @kevmoo ) |
Hey @alestiago I completely forgot about this, No it's not being worked on from my side. If you want we can work on this together. |
@AliAkberAakash I don't have the bandwidth right now to work on this feature. If I ever have some spare I'll let you know. If you're no longer working on this I recommend asking to get unassigned. |
So I know in general that YAML is a superset of JSON, but Is there any sort of valid Pubspec that can't be represented by JSON, though? I threw this together pretty quickly -- is something like this a good starting point for a PR?
|
Adding the above |
It's fantastic to have an official package on Pub for parsing and extracting data from a pubspec.
There is, however, one thing, I'm wondering - would it be bad for
createToJson
to betrue
for the models contained in this package?I'm working on updating the Angel CLI, which uses the old
package:pubspec
to persist changes to the project files (namely, adding dependencies the user is missing), topubspec_parse
, and if there were some way to just get atoJson
method on thePubSpec
.I'll gladly send a PR, but is there is a specific reason this functionality isn't present already? I imagine there's probably a reason I didn't think about.
The text was updated successfully, but these errors were encountered: