This repository has been archived by the owner on Jun 3, 2024. It is now read-only.
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.
params
in navigation actions tostate
, which is what they actually are. This has been done to avoid confusion with route params and query params.events
in navigation. Navigation events allows the next page to report something to the calling page. Whilestate
send information from the calling page to the target page,events
do the opposite.triggerViewEvent
which triggers anevent
passed in the navigation. It accepts the event name and the value for the implicit state to be created.object
. This is necessary because Nimbus Script has no support for object literals yet. With this operation, one can create an object by calling@{object('key1', 1, 'key2': 'hello', 'key3', true)}
for instance.array
. This is necessary because Nimbus Script has no support for array literals yet. With this operation, one can create an array by calling@{array('element1', 2, 'element3', 4, null, 6)}
for instance.