Update proxy paths in Netlify documentation#16302
Open
Conversation
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 0 errors, 10 warnings, 2 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules!
|
| Line | Severity | Message | Rule |
|---|---|---|---|
| 13:66 | warning | Use 'Netlify' instead of 'netlify'. | Vale.Terms |
| 17:225 | suggestion | Address the reader directly. Use 'you' instead of 'the user'. | PostHogDocs.DirectAddress |
| 25:42 | suggestion | Address the reader directly. Use 'you' instead of 'the user'. | PostHogDocs.DirectAddress |
| 33:107 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 50:6 | warning | Use 'Netlify' instead of 'netlify'. | Vale.Terms |
| 53:4 | warning | 'Option 1: netlify.toml' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 53:14 | warning | Use 'Netlify' instead of 'netlify'. | Vale.Terms |
| 94:131 | warning | 'proxying' is a possible misspelling. | PostHogBase.Spelling |
| 106:69 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 219:69 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 296:32 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 301:5 | warning | 'CORS errors' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
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
1 participant
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.
Changes
We've learned from experience that suggestions we make / examples we use for reverse proxy naming will eventually be spotted and blocked by adblockers.
/ingestwas a suggestion that used to be in our docs and was later removed from our docs after we spotted it in adblocking/anti-tracking lists.So, changing instance of this:
/phto this:
/yourpath