You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously we developed a utility called askUser() allowing us to create multi-step text user inputs.
While the current solution wraps the native InputBox API, it still doesn't support the native QuickPick API which lets the user pick an item from a list of items. Without it, we cannot augment the UX of our Troubleshooting flow (going back to select another answer, cleaner code, etc) and we also won't have it ready to use when we'll definitely need it in the future.
Luckily the existing architectural design already accounts for this future expansion (in reality development of the feature was cut short due to time constraints).
Acceptance Criteria:
askUser() accepts Question definitions where kind can additionally have the value 'single-select' or 'multi-select' corresponding to the QuickPick.canSelectMany option
existing uses of the QuickPick API across the codebase are replaced with askUser()
The text was updated successfully, but these errors were encountered:
Previously we developed a utility called
askUser()
allowing us to create multi-step text user inputs.While the current solution wraps the native InputBox API, it still doesn't support the native QuickPick API which lets the user pick an item from a list of items. Without it, we cannot augment the UX of our Troubleshooting flow (going back to select another answer, cleaner code, etc) and we also won't have it ready to use when we'll definitely need it in the future.
Luckily the existing architectural design already accounts for this future expansion (in reality development of the feature was cut short due to time constraints).
Acceptance Criteria:
askUser()
acceptsQuestion
definitions wherekind
can additionally have the value'single-select'
or'multi-select'
corresponding to theQuickPick.canSelectMany
optionaskUser()
The text was updated successfully, but these errors were encountered: