Skip to content
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.

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

Use route provider, not statically generated YAML routes, for content entities #2020

Open
Crell opened this issue Mar 11, 2016 · 4 comments
Open

Comments

@Crell
Copy link
Contributor

Crell commented Mar 11, 2016

And probably for config entities, too. 😄

We're trying to actively discourage manually created routes for entities. Instead, the generated annotation should reference the default route provider. It will then generate appropriate routes on the fly based on the links array on the entity.

@bojanz
Copy link
Contributor

bojanz commented Mar 14, 2016

Where are you seeing static routes? Both content and config entities use the DefaultHtmlRouteProvider.

@bojanz
Copy link
Contributor

bojanz commented Mar 14, 2016

Related: #2022 (since it will remove the custom add-form implementation)

@Crell
Copy link
Contributor Author

Crell commented Mar 14, 2016

Hm, perhaps I have an old copy of console installed? I generated a content entity, and ended up with several new routes defined. (I've since deleted them as this entity doesn't even have a UI.)

@hjuarez20
Copy link
Contributor

See #1849, we will change the way how we render the routes

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

No branches or pull requests

4 participants