-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Split rustdoc JSON types into separately versioned crate #81287
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
r? @jyn514 |
The job Click to see the possible cause of the failure (guessed by this bot)
|
The job Click to see the possible cause of the failure (guessed by this bot)
|
Could you provide more information about this please? Why making it a standalone library would be better for example? |
See this conversation for the details: https://rust-lang.zulipchat.com/#narrow/stream/266220-rustdoc/topic/JSON.20Format/near/223685843 |
Ok I see, makes sense. However, could you move this library outside of |
@jyn514 advised me to put it in librustdoc, so I'd like to give him a chance to comment first. If he agrees, I'll move it. |
You're right, let's maybe talk about it before you make any further changes. ;) |
I would prefer to keep this in librustdoc. It will only be used by rustdoc ( |
I disagree. We have split all sub-crates and put them in their own folders for the compiler, so I think we should do the same here since the end goal is to put it out of tree. If the |
Ok, then |
Sounds good to me! |
Alright, if |
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.
r=me with the directory renamed to src/etc/json-types.
etc seems like a really bad place. I'm worried we might be blanket copying that directory for dist too somewhere. Can we do src/rustdoc-json-types? |
Moved the crate, and updated all the relevant files |
@bors r+ |
📌 Commit 36284a3 has been approved by |
☔ The latest upstream changes (presumably #80987) made this pull request unmergeable. Please resolve the merge conflicts. |
6cbc4c2
to
67b78a0
Compare
Merge conflict fixed, checks are green |
Thanks! @bors r=jyn514,GuillaumeGomez squash |
📌 Commit 3aa8456 has been approved by |
Rollup of 10 pull requests Successful merges: - rust-lang#79570 (rustc: Stabilize `-Zrun-dsymutil` as `-Csplit-debuginfo`) - rust-lang#79819 (Add `SEMICOLON_IN_EXPRESSIONS_FROM_MACROS` lint) - rust-lang#79991 (rustdoc: Render HRTB correctly for bare functions) - rust-lang#80215 (Use -target when linking binaries for Mac Catalyst) - rust-lang#81158 (Point to span of upvar making closure FnMut) - rust-lang#81176 (Improve safety of `LateContext::qpath_res`) - rust-lang#81287 (Split rustdoc JSON types into separately versioned crate) - rust-lang#81306 (Fuse inner iterator in FlattenCompat and improve related tests) - rust-lang#81333 (clean up some const error reporting around promoteds) - rust-lang#81459 (Fix rustdoc text selection for page titles) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
rustdoc-json: Fix has_body Previously, `has_body` was always true. Now propagate the type of the method to set it correctly. Relies on rust-lang#81287, that will need to be merged first.
rustdoc-json: Fix has_body Previously, `has_body` was always true. Now propagate the type of the method to set it correctly. Relies on rust-lang#81287, that will need to be merged first.
rustdoc-json: Fix has_body Previously, `has_body` was always true. Now propagate the type of the method to set it correctly. Relies on rust-lang#81287, that will need to be merged first.
rustdoc-json: Fix has_body Previously, `has_body` was always true. Now propagate the type of the method to set it correctly. Relies on rust-lang#81287, that will need to be merged first.
@rustbot modify labels: +A-rustdoc-json |
For now just an in-tree change.
In the future, this may be exposed as a standalone crate with standard semver.