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
When using a static subdomain constraint, it would make sense to implicitly set the subdomain as a default. As it is right now, that has to happen explicitly:
But since the routes inside the constraint block are inaccessible to other subdomains, having to define the default here feels redundant. This would be more elegant:
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.
-
When using a static subdomain constraint, it would make sense to implicitly set the subdomain as a default. As it is right now, that has to happen explicitly:
But since the routes inside the constraint block are inaccessible to other subdomains, having to define the default here feels redundant. This would be more elegant:
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions