-
Notifications
You must be signed in to change notification settings - Fork 2
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
fix: update typesVersion
field spec to match docs
#3
Conversation
It could be good to check that the keys of the |
Seems like because I updated the dependencies, it pulls in a newer version of dprint in which something in the current config doesn't work, making the |
Thanks for the PR. I'll take a look now. |
@@ -66,8 +66,8 @@ pub struct PackageJson { | |||
#[builder(default, setter(into, strip_option))] | |||
pub version: Option<String>, | |||
|
|||
/// Version must be parseable by node-semver, which is bundled with npm as a | |||
/// dependency. | |||
/// Put a description in it. It's a string. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why change this?
Cargo.toml
Outdated
validator = { version = "0.16", features = ["derive"], optional = true } | ||
proc-macro2 = "1.0.66" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does this do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's leftover of me trying to fix the CI checks. I'll tidy things up shortly.
@ifiokjr PR cleaned up and ready for review |
typesVersion
field spec to match docs
Hi! The library is throwing errors on valid documented usage of the
typesVersions
field, so this fixes that.[Documentation so
(also, I added therustfmt.toml
file to make all future contributions respect your indent style)