-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Improve crate manifests, adding missing [package.repository]
and [package.description]
fields
#17745
Conversation
crates/base-db/Cargo.toml
Outdated
@@ -1,7 +1,8 @@ | |||
[package] | |||
name = "base-db" | |||
version = "0.0.0" | |||
description = "TBD" | |||
repository = "https://github.com/rust-lang/rust-analyzer" | |||
description = "Basic database traits. The concrete DB is defined by `ra_ap_ide`." |
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.
Bah, feels like this should say ide
.
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.
I changed it to ra_ap_ide
as that's the name that the crate is currently published as. As such anyone reading the description on crates.io would be tempted to search for ide
but not find anything (or worse even, be lead to a completely different unrelated and mostly empty ide
crate).
Happy to change it back to ide
though, if that's the consensus of what it should be referred to as.
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.
Can we just do something like ide/ra_ap_ide
then?
It's a bit confusing how half of these say "for rust-analyzer" and half don't. |
Agreed. I was leaning towards adding it to give people stumbling upon a For others adding it felt a bit verbose though, so I omitted it as I wanted to stay true to the crate's module docs. Having an inconsistent mix definitely isn't optimal though as it begs the question of "is crate I'm happy with whatever you —the maintainers— prefer. |
@Veykril do you have an opinion on this (as well as the |
crates/hir-def/Cargo.toml
Outdated
@@ -1,7 +1,8 @@ | |||
[package] | |||
name = "hir-def" | |||
version = "0.0.0" | |||
description = "TBD" | |||
repository = "https://github.com/rust-lang/rust-analyzer" | |||
description = "Everything between macro expansion and type inference for rust-analyzer." |
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.
description = "Everything between macro expansion and type inference for rust-analyzer." | |
description = "Early name and import resolution for rust-analyzer." |
might be more fitting
crates/proc-macro-api/Cargo.toml
Outdated
@@ -1,7 +1,8 @@ | |||
[package] | |||
name = "proc-macro-api" | |||
version = "0.0.0" | |||
description = "TBD" | |||
repository = "https://github.com/rust-lang/rust-analyzer" | |||
description = "Client-side proc-macros for rust-analyzer." |
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.
description = "Client-side proc-macros for rust-analyzer." | |
description = "RPC Api for the `proc-macro-srv`. |
crates/syntax/Cargo.toml
Outdated
repository = "https://github.com/rust-lang/rust-analyzer" | ||
description = "Comment and whitespace preserving parser for the Rust language" |
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.
description = "Comment and whitespace preserving parser for the Rust language" | |
description = "Concrete syntax tree definitions for rust-analyzer" |
@bors delegate+ |
✌️ @regexident, you can now approve this pull request! If @Veykril told you to " |
not sure whats up with CI, it runs on nightly given the changes so there might be something breaking for us on latest nightly |
5f25256
to
2bd7ed1
Compare
@Veykril FYI I've applied your suggested changes and also added any missing mentions of rust-analyzer (cc @lnicola ) with the following reasoning: With the lack of a README on the individually published library crates and the somewhat cryptic This is quite a bit more than your suggested changes though, so … … just to be sure you're good with those changes. The PR can be merged you're happy with it. |
Improve crate manifests, adding missing `[package.repository]` and `[package.description]` fields As [discussed on Zulip](https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer/topic/Could.20we.20add.20repository.20url.20to.20.60ra_ap_.60.20crates.20on.20crates.2Eio.3F/near/455095161). cc `@Veykril` `@lnicola`
💔 Test failed - checks-actions |
crates/base-db/Cargo.toml
Outdated
@@ -1,7 +1,8 @@ | |||
[package] | |||
name = "base-db" | |||
version = "0.0.0" | |||
description = "TBD" | |||
repository = "https://github.com/rust-lang/rust-analyzer" |
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.
repository = "https://github.com/rust-lang/rust-analyzer" | |
repository.workspace = true |
Nit, this should be workspace inehritable no?
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.
Now that you mention it, yes of course! Fixed.
CI should succeed again after #17794 is merged |
…package.description]` fields
With the lack of a README on the individually published library crates and the somewhat cryptic `ra_ap_` prefix it is hard to figure out where those crates belong to, so mentioning "rust-analyzer" feels like auseful hint there.
72dd3aa
to
868deab
Compare
…ge.repository.workspace] = true`
868deab
to
7dec7e9
Compare
Thanks! |
☀️ Test successful - checks-actions |
@regexident there's one more if you want (syntax-bridge). |
…n, r=lnicola Improve crate manifest of 'syntax-bridge', adding missing `[package.repository]` and `[package.description]` fields This is a follow-up of #17745, specifically [this comment](#17745 (comment)) by `@lnicola.` It refines the manifest of the newly added 'syntax-bridge' crate, adding a `[package.repository]` as `workspace = true` and changes the existing `[package.description]` from "TBD" to a more useful description.
…ntinuation, r=lnicola Improve crate manifest of 'syntax-bridge', adding missing `[package.repository]` and `[package.description]` fields This is a follow-up of rust-lang/rust-analyzer#17745, specifically [this comment](rust-lang/rust-analyzer#17745 (comment)) by `@lnicola.` It refines the manifest of the newly added 'syntax-bridge' crate, adding a `[package.repository]` as `workspace = true` and changes the existing `[package.description]` from "TBD" to a more useful description.
As discussed on Zulip.
cc @Veykril @lnicola