Conversation
Contributor
|
with you on the not-so-good practice of FLP navigation...but I'd favor the above to be in the |
Contributor
|
re-pinging you @Siolto for your opinion on rather updating the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
How we currently suggest to navigate in the FLP is more of a bad practice than a good one. In my opinion there are 3 better ways to do that:
baseUrlto your application (with semantic object and action). That way you save also time while not waiting for the launchpad to load.If you really want to start with a launchpad:
wdi5.goTo("#semanticObject-action")function to navigate to one specific application in the launchpadIf you really want to identify the tile via wdi5:
All three ways are better than our current one where we suggest to programmatically navigate the control tree up.