-
Notifications
You must be signed in to change notification settings - Fork 175
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
Implement dynamic route titles #2590
Conversation
Plus * Add a missing @test annotation * Add a comment to explain an unclear code part
Reviewed 5 of 8 files at r1, 3 of 3 files at r2. flow-server/src/main/java/com/vaadin/router/NavigationStateRenderer.java, line 251 at r2 (raw file):
I think the requirement in javadoc of flow-server/src/main/java/com/vaadin/router/NavigationStateRenderer.java, line 254 at r2 (raw file):
Isn't Also there is flow-server/src/main/java/com/vaadin/server/startup/RouteRegistryInitializer.java, line 72 at r2 (raw file):
It might me that another method should be used for inherited annotations. By the way what about situation: class has Comments from Reviewable |
Review status: 8 of 9 files reviewed at latest revision, 6 unresolved discussions, some commit checks failed. flow-documentation/routing/tutorial-routing-page-titles.asciidoc, line 41 at r3 (raw file):
all source parts need to also be added to a java class. in this case to flow-server/src/main/java/com/vaadin/router/NavigationStateRenderer.java, line 254 at r2 (raw file): Previously, denis-anisimov (Denis) wrote…
Title should only be taken from the activated navigation target and parents should not be taken into account. When section titles is implemented then the title for the activated navigation target is sent to all parent layouts so that they may update or replace the title. flow-server/src/main/java/com/vaadin/server/startup/RouteRegistryInitializer.java, line 72 at r2 (raw file): Previously, denis-anisimov (Denis) wrote…
As replied above, parent layout title information should not be considered in any way for this as it's only a restriction for the route target. Comments from Reviewable |
Reviewed 1 of 1 files at r3. flow-server/src/main/java/com/vaadin/router/NavigationStateRenderer.java, line 254 at r2 (raw file): Previously, caalador wrote…
Oh, I misread the code, my bad. Comments from Reviewable |
Also fix a typo
Review status: all files reviewed at latest revision, 6 unresolved discussions, some commit checks failed. flow-server/src/main/java/com/vaadin/router/NavigationStateRenderer.java, line 251 at r2 (raw file): Previously, denis-anisimov (Denis) wrote…
It is already enforced at startup time, in flow-server/src/main/java/com/vaadin/server/startup/RouteRegistryInitializer.java, line 72 at r2 (raw file): Previously, caalador wrote…
Hmmm... good point! Added a test case for it. Comments from Reviewable |
Review status: all files reviewed at latest revision, 5 unresolved discussions, some commit checks failed. flow-documentation/routing/tutorial-routing-page-titles.asciidoc, line 41 at r3 (raw file): Previously, caalador wrote…
Done. Comments from Reviewable |
Reviewed 2 of 3 files at r4. flow-server/src/test/java/com/vaadin/router/RouterTest.java, line 467 at r4 (raw file):
This should not set the title. Only title from the routeTarget is to be used. Comments from Reviewable |
Review status: 9 of 10 files reviewed at latest revision, 2 unresolved discussions. flow-server/src/test/java/com/vaadin/router/RouterTest.java, line 467 at r4 (raw file): Previously, caalador wrote…
Done. Comments from Reviewable |
Make the renderer not consider parent views when looking for @title
Reviewed 1 of 3 files at r4, 3 of 3 files at r5. Comments from Reviewable |
Code needs fixes after merging master. |
Reviewed 1 of 1 files at r6, 2 of 2 files at r8. Comments from Reviewable |
Plus
@Test
annotationFixes #2397
This change is