internal: Publish test-fixture => ra_ap_test_fixture #18437
Merged
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rustbot
added
the
S-waiting-on-review
Veykril
approved these changes
Oct 31, 2024
lnicola
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently it's possible to build rust-analyzer from the ra_ap crates, but not
possible to build their tests, as test-fixture isn't published.
If there isn't a particular reason to exclude this crate, I'd like to publish
it so that tests can be built and run from crates.io sources.
Context: I'm importing rust-analyzer code into a non-cargo build environment
(using Bazel). We'd prefer to import from crates.io for uniformity with other
libraries, and to build and run all tests to make sure we didn't break anything.