fix: manage route prefix #336
Merged
Conversation
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
alanpoulain
force-pushed
the
fix/prefix
branch
from
b9039d4 to
4785da1
Compare
alanpoulain
force-pushed
the
fix/prefix
branch
2 times, most recently
from
f025353 to
9184f83
Compare
alanpoulain
force-pushed
the
fix/prefix
branch
from
9184f83 to
3fe7476
Compare
This was referenced Aug 29, 2022
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.
Replaces #314.
Instead of #314, route prefix does not change how the pages are generated.
A
getPathhelper function allows to get the corresponding path from an IRI having a prefix.This PR also adds E2E tests for Nuxt.