Add more non-platform extensions to dev services guide + make guide guide-ier #39913
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
|
I think Neo4j was in there because it was part of the core repository at some point. |
Yeah, I came to the same conclusion. |
This comment has been minimized.
This comment has been minimized.
3 tasks
…re closely match the "dev services overview" title.
holly-cummins
force-pushed
the
dev-services-ecosystem
branch
from
a460446
to
0e1733c
Compare
Status for workflow
|
gsmet
approved these changes
Apr 7, 2024
|
Nice, thanks! |
|
🙈 The PR is closed and the preview is expired. |
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.
It's been a pain point for me for a while that the dev services guide, https://quarkus.io/guides/dev-services, is more of a reference which lists available dev services. The title calls it "Dev Services Overview" and we link to it in that context, but it's would be hard to learn much about dev services, just from that document. I've added a bit more information, and also a few more headings, just to visually bulk up the "this document tells you what a dev service is and how you might use it" section of the document.
The other thing this change does is resolves quarkusio/quarkusio.github.io#1869, which was created in response to quarkiverse/quarkus-wiremock#70. At the moment the decision about what dev services to include is a bit arbitrary - it's mostly platform-only, but Neo4J is in there.
Longer term, hand-curating a list of every ecosystem extension isn't very scalable, so we'll want to investigate automation, and also a solution to the "how can I find out what extensions have dev services?" question. I've raised quarkusio/extensions#983 to partially cover that requirement.