Repository navigation
docs: give Echo Pro and Echo Support their own README section - #3203
Merged
Merged
Conversation
List Echo Pro and commercial support next to community help at the top, and describe both in a short section after Features. Tighten feature wording: state the router's matching order, note that Let's Encrypt works through autocert, and drop filler comments from the example.
vishr
changed the title
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.
Makes Echo Pro and Echo Support visible in the master README, following common open-core patterns (edition note near the top as in AG Grid and Ory, own section as in NestJS, commercial support next to community help as in react-admin and Sidekiq).
autocert, no filler comments in the example.All links return 200; the example compiles against v5.4.4. Reviewed by Codex twice: no findings.