Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Invalid compiled page name in windows on version 1.0.0-canary.1 #361

Closed
vimutti77 opened this issue Dec 2, 2020 · 1 comment
Closed

Invalid compiled page name in windows on version 1.0.0-canary.1 #361

vimutti77 opened this issue Dec 2, 2020 · 1 comment
Milestone
1.0.0

Comments

@vimutti77
Copy link
Contributor

vimutti77 commented Dec 2, 2020 •
edited
Loading

In next-translate v1.0.0-canary.1, If I have a page in pages/foo/bar. The compiled page pathname that need to use in i18n.json will be /foar.

Expected behavior

Page location: pages/foo/bar
Compiled page pathname: /foo/bar

Compiled log

next-translate - compiled page: /foo/bar - locale: en - namespaces: common, error - used 
loader: getStaticProps

Actual behavior

Page location: pages/foo/bar
Compiled page pathname: /foar

Compiled log

next-translate - compiled page: /foar - locale: en - namespaces: common, error - used 
loader: getStaticProps
@vimutti77 vimutti77 changed the title Page name does not contain / between path in version 1.0.0-canary.1 Compiled page name does not contain / between path in version 1.0.0-canary.1 Dec 2, 2020
@vimutti77 vimutti77 changed the title Compiled page name does not contain / between path in version 1.0.0-canary.1 Invalid Compiled page name in windows in version 1.0.0-canary.1 Dec 2, 2020
@vimutti77 vimutti77 changed the title Invalid Compiled page name in windows in version 1.0.0-canary.1 Invalid compiled page name in windows on version 1.0.0-canary.1 Dec 2, 2020
@vimutti77 vimutti77 mentioned this issue Dec 2, 2020
Merged
@aralroca
Copy link
Owner

aralroca commented Dec 2, 2020

Already prereleased on 1.0.0-canary.2 😜. Thanks @vimutti77

@aralroca aralroca closed this as completed Dec 2, 2020
@aralroca aralroca added this to the 1.0.0 milestone Dec 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
2 participants
@aralroca @vimutti77