[ https://issues.jboss.org/browse/ARQGRA-500?page=com.atlassian.jira.plugin... ] Vsevolod Golovanov commented on ARQGRA-500: ------------------------------------------- Dumping some additional concerns that bother me. -- Generalize to dynamic path manipulation (DPM)? "Parameters" only make sense for the HTTP scheme currently. The linked SO's OP also wanted more than that. But generalize too much and it looks like another LocationDecider. Might as well check if the test object implememts the LocationDecider interface. No, I think the generalized DPM should be an implementation helper for Deciders. E.g. the HTTP decider would use it to implement the parameter provider functionality and path substitution functionality ("http://static/\{dynamic\}") - 2 different interfaces. But how to expose this functionality in Graphene.goTo? Either be content with some generic DPM interface argument, or refactor goTo to return a specific builder somehow. Make goTo return a builder? Nasty breaking change - goTo now doesn't trigger navigation. Some new method (arguments like goTo) returns a builder, and an argumentless goTo triggers navigation? This could work. -- Need to descriminate the pages. Problem: LocationDecider only knows a String location. Needs to know pageClass too. --- Annotated parameters could accept it as {{\@LocationParameters(for = MyPage.class)}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)