New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve the spec's understanding of routes #640

Open

squeed opened this issue Mar 13, 2019 · 0 comments

Member

squeed commented Mar 13, 2019

Routes right now are not rigorously specified.

For example,

Routes without a gateway are inconsistently handled in plugins
The spec doesn't actually say where the routes should be applied
Not all use cases can be expressed (e.g. flagging routes as local)

We should improve this in a future version of the spec.

This was referenced Feb 20, 2024

Add table ID property for routes #1062

Merged

Add Scope property for routes #1068

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment