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
It's easy to end up with multiple routes with the same path by mistake, especially when playing around with the platform and copypasting examples from docs, so this is a fairly common scenario. The problem is that the resulting stack trace does not make it easy to understand what the problem is.
Could the framework print a clear and unambiguous error in the output when this is encountered, instead of relying on a cryptic stacktrace?
The text was updated successfully, but these errors were encountered:
It's easy to end up with multiple routes with the same path by mistake, especially when playing around with the platform and copypasting examples from docs, so this is a fairly common scenario. The problem is that the resulting stack trace does not make it easy to understand what the problem is.
Could the framework print a clear and unambiguous error in the output when this is encountered, instead of relying on a cryptic stacktrace?
The text was updated successfully, but these errors were encountered: