Repository navigation
Conversation
Turn the Community Tools section into an alphabetical table with lowercase tags, and teach the ecosystem order check to read those rows. Core and Community stay lists. Refs: fastify#3618 Signed-off-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: whoalin1 <whoalin1@users.noreply.github.com>
This file contains hidden or 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
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.
Refs fastify#3618
Summary
docs/Guides/Ecosystem.mdinto a table with a lowercasetagscolumn.This is a first slice of fastify#3618, limited to the shortest section. It follows the review on fastify#6518: keep the current order and add a tags column, instead of introducing category headings. fastify#4938 settled on the same shape, with lowercase tags.
Website follow-up
fastify/websitescripts/build-plugin-list.mjsonly reads markdown list items. After this change, the seven Community Tools entries drop out ofplugins.jsonuntil that script reads table rows. Core and Community are unchanged, so the rest of the ecosystem page is unaffected. The guide page itself renders the table.Test plan
node --test test/scripts/lint-ecosystem.test.jsnpm run lint:markdown(tables are exempt from the line-length rule)