Skip to content
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.

feat: navigation callbacks #75

Merged
merged 2 commits into from
Jan 12, 2023
Merged

feat: navigation callbacks #75

merged 2 commits into from
Jan 12, 2023

Conversation

Tiagoperes
Copy link
Contributor

@Tiagoperes Tiagoperes commented Jan 11, 2023

  • Renames params in navigation actions to state, which is what they actually are. This has been done to avoid confusion with route params and query params.
  • Implemented events in navigation. Navigation events allows the next page to report something to the calling page. While state send information from the calling page to the target page, events do the opposite.
  • Implemented action triggerViewEvent which triggers an event passed in the navigation. It accepts the event name and the value for the implicit state to be created.
  • State declaration now accepts expressions! i.e. a state can be initialized with the value of another state or operation.
  • New operation: 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.
  • New operation: 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.

…y; expressions on initial value of states. Renamed params on navigation to state.
@arthurbleilzup arthurbleilzup merged commit 542681a into main Jan 12, 2023
@arthurbleilzup arthurbleilzup deleted the feat/navigation-callback branch January 12, 2023 14:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants