-
Notifications
You must be signed in to change notification settings - Fork 174
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 intent based navigation #1634
Implement intent based navigation #1634
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job @ndricimrr , only few minor comments.
test/e2e-test-application/src/app/project/project.component.html
Outdated
Show resolved
Hide resolved
Co-authored-by: Aleksandra Simeonova <[email protected]>
Co-authored-by: Aleksandra Simeonova <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work 🥇
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added few extra minor suggestions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems there is no need to use let
declaration for string replacing. It replaces instances of a substring with another substring, and returns the modified string.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! Thanks @ndricimrr
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some questions :)
client/src/linkManager.js
Outdated
@@ -61,12 +62,14 @@ export class linkManager extends LuigiClientBase { | |||
|
|||
this.options.preserveView = preserveView; | |||
const relativePath = path[0] !== '/'; | |||
const intentPath = path.includes('?Intent='); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to allow or prefer lowercase intent? camelcase is somehow a bit unusual for parameters
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤔 will ask this in afterscrum too 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
talked w/Philipp and chose to go with case insensitive for this one so Intent and intent (+any other case insensitive combination of the keyword "intent") should now work.
Co-authored-by: Markus <[email protected]>
…uigi into 1605-intent-based-navigation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job Jimmy 👍
Description
To test
LuigiClient.linkManager().navigate('#?Intent=Sales-edit?id=100')
The intent identifier matching pattern can be case insensitive: ?Intent= || ?intent= || ?INTENT= || ....
semanticObject
must be alphanumeric.action
can contain alphanumeric characters and also the underscore sign '_'semanticObject
and action areseparated
by a hyphen '-' character, which is illegal to use within either of those.http://localhost:4200/#Sales-settings?
even after page refresh or subsequent URL change.References for documentation:
Fiori Launch Pad > Configuring Navigation
Fiori Launch Pad > Intent Based Navigation
SAP Hana Developer Guide> Intent Based Navigation in App Launcher Tiles
Navigation to a Semantic Object