<div dir="ltr">I like the idea.<div><br></div><div>I'm not fan of angular router either.</div><div><br></div><div><br></div><div>David</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 9, 2016 at 3:01 AM, Ondrej Zizka <span dir="ltr"><<a href="mailto:ozizka@redhat.com" target="_blank">ozizka@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Devs.<br>
<br>
In Angular, I miss a good routing mechanism like other web frameworks have<br>
<br>
Angular:<br>
<br>
editApplication(application: RegisteredApplication) {<br>
this._router.navigate(['/edit-<wbr>application', <a href="http://application.id" rel="noreferrer" target="_blank">application.id</a>]);<br>
}<br>
<br>
Other framework:<br>
<br>
public void editApplication(Application application) {<br>
setResponsePage(<wbr>ApplicationPage.class, new<br>
PageParameters().add("app", application));<br>
}<br>
<br>
Which is often shortened, if the components implements an interface,<br>
<br>
setResponsePage(<wbr>ApplicationPage.navigate(<wbr>application));<br>
<br>
<br>
How about creating a Navigator which would work similarly.<br>
<br>
editApplication(application: RegisteredApplication) {<br>
this._navigator.navigate(<wbr>ApplicationComponent, application);<br>
}<br>
<br>
The advantage is that it's type safe and the constants are at a single<br>
point rather than scattered across the web app (or at the component's<br>
class).<br>
<br>
WDYT?<br>
<br>
Ondra<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
--<br>
Ondrej Zizka, Windup project, Brno<br>
<br>
______________________________<wbr>_________________<br>
windup-dev mailing list<br>
<a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/windup-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/windup-dev</a><br>
</font></span></blockquote></div><br></div>