Consider panicking when `nest` would overwrite resources
Open
design
- Dominant language
- Rust
- Stars
- 5.1k
- Forks
- 329
- PR merge metrics
- No merged PRs in 30d
Description
Right now, calling `nest` on a route that already has resources causes those resources to be silently dropped, which seems problematic. We should either figure out a reasonable way to "merge" with existing resources (I'm skeptical this would work out), or just panic in such a case.
Panicking in app construction is generally OK since even trivial testing will reveal the problem.
Contributor guide
Assessment
This issue has not been assessed yet.