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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we just need a check that the [name] positional argument to these generators can't start with a /. This would be used in any generator that creates a file:
cell
component
dataMigration
directive
function
layout
model
page
scaffold
script
sdl
service
Here is the current action:
$ yarn rw g page /test
← Reverted because: Unexpected token, expected "}" (15:27)
13 | <p>
14 | My default route is named <code>c:/programFiles/git/test</code>, link to me with `
15 | <Link to={routes.c:/programFiles/git/test()}>CProgramFilesGitTest</Link>`
| ^
16 | </p>
17 | </>
18 | )
◼ Updating routes file...
◼ Generating types...
◼ One more thing...
and
$ yarn rw g page /
← Reverted because: Unexpected token, expected "}" (15:27)
13 | <p>
14 | My default route is named <code>c:/programFiles/git/</code>, link to me with `
15 | <Link to={routes.c:/programFiles/git/()}>CProgramFilesGit</Link>`
| ^
16 | </p>
17 | </>
18 | )
How do we reproduce the bug?
run yarn rw g page /
What's your environment? (If it applies)
No response
Are you interested in working on this?
I'm interested in working on this
The text was updated successfully, but these errors were encountered:
@pantheredeye Could you share your Routes.tsx file and show what the route is actually named? And the generator command you uses to create a page? Your goal was to "to create nested pages"?
What's not working?
Related Closed Issue
The generator cli tool is not preventing using
/
at the beginning of the .The generator cli should prevent using
/
at the beginning of the name. It should allow/
after the first character to create nested pages.from this comment and related issue:
Here is the current action:
and
How do we reproduce the bug?
run
yarn rw g page /
What's your environment? (If it applies)
No response
Are you interested in working on this?
The text was updated successfully, but these errors were encountered: