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
For example, 'invoices/all:invoicename' for 'invoices/allgood','invoices/allbad','invoices/allfinished'...
And the filename can be ' [all]{$invoicename}' or ' all' perhaps.
invoices
├── [all]{$invoicename}.tsx
For example, 'things/pro:name' for 'things/probook','things/promouse','things/procup'...
And the filename can be ' [pro]{$name}' or ' pro' perhaps.
things
├── [pro]{$name}.tsx
The prefixes are not suitable to be a segment. They are too short or Meaningless.
Suffixes can also be considerated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I want a prefix for a route dynamic segment.
For example, 'invoices/all:invoicename' for 'invoices/allgood','invoices/allbad','invoices/allfinished'...
And the filename can be ' [all]{$invoicename}' or ' all' perhaps.
invoices
├── [all]{$invoicename}.tsx
For example, 'things/pro:name' for 'things/probook','things/promouse','things/procup'...
And the filename can be ' [pro]{$name}' or ' pro' perhaps.
things
├── [pro]{$name}.tsx
The prefixes are not suitable to be a segment. They are too short or Meaningless.
Suffixes can also be considerated.
Beta Was this translation helpful? Give feedback.
All reactions