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
My concern is if someone (user or crawler) has somewhere cached that https://eslint.org/docs/user-guide/configuring/ redirects to https://eslint.org/docs/user-guide/configuring (current URL), what will happen when we release the new version where https://eslint.org/docs/user-guide/configuring redirects back to https://eslint.org/docs/user-guide/configuring/ (new URL).
Hopefully, it will ask again for https://eslint.org/docs/user-guide/configuring/ before treating this as a cyclic redirect.
What's our backup plan if it turns out the preexisting 301 from configuring/ to configuring ends up breaking something in combination with the new 301 from configuring back to configuring/? Rename the new docs to configuration/ and redirect configuring/? there?
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.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.