NextStep and selectNext async typing updates #1278
Merged
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
NextSteptype to allow specifying an async function that resolves with the string of the next pageselectNexttype to indicate it returns the result of anyNextStepfunction provided to itNextStepfunction parameter type to match current implementationI've listed as a
fixbecause this is just a type change, but can list as afeatif anybody is concerned about breaking existing types.I didn't update documentation as I'm not sure if you wanted to have this be mentioned in the standard
Wizarddocs since it's not supported by anything other than custom wizards.Checklist: (please see documentation page for more information)
Yarn buildpassesYarn lintpassesYarn testpassesfix|feat({scope}): {description}fix(pf3): wizard correctly handles next buttonFix button on documenation example page