Skip to content

Router: throw exception if there's an ambiguous route #699

@g105b

Description

@g105b

All routes should be obvious: either from the URI you should be able to know exactly what file executes, or from a page view/logic you should be able to know what URI is used.

There is one ambiguity:

  • page/blog/index.html
  • page/blog.html

These could both be triggered by the path /blog... which one should WebEngine pick?

An AmbiguousPathException should be thrown IMO.

Metadata

Metadata

Assignees

Labels

enhancementNon-breaking improvements to existing behaviour

Type

No fields configured for Task.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions