Hey guys. I was wondering if anyone else would be interested in
expanding the page navigation path support. Currently I think
@Page(path="blah") only supports relatively basic tokens. Additionally,
the @PageState feature expresses the state values similar to query params.
What I would like to do is something like this:
@Templated
@Page(path="/{customerId}/orders/{orderId}")
public class OrderDetailsPage extends Composite {
@PageState String customerId;
@PageState String orderId;
}
This would allow a very flexible system for generating interesting URLs.
So the URL for my app might look like:
http://example.org/myapp#/CustomerABC/orders/order-17
Does anyone else desire something like this?
-Eric