Make navigateToIntent parameters optional #2226
Merged
Conversation
This file contains 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
ndricimrr
requested review from
alexandra-simeonova,
hardl,
JohannesDoberer,
rafalgamon,
stanleychh,
UlianaMunich and
wdoberschuetz
as code owners
wdoberschuetz
approved these changes
Aug 25, 2021
alexandra-simeonova
approved these changes
Aug 25, 2021
Merged
stanleychh
pushed a commit
to stanleychh/luigi
that referenced
this pull request
Dec 30, 2021
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.
Description
Noticed during trying it out on different scenario that parameters must be optional type, as one can navigate to an intent mapping with/without any parameters.
Changes proposed in this pull request:
navigateToIntent(semanticSlag: string, params: Object)changed to:
navigateToIntent(semanticSlag: string, params?: Object)as parameters should be optional.
Related issue(s)