Remove unnecessary steps in explorer/converter modals#300
Merged
cristian-tamblay merged 1 commit intoSep 22, 2025
Conversation
cristian-tamblay
approved these changes
Sep 22, 2025
This file contains hidden or 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
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.
This pull request streamlines the notebook tool configuration workflow by conditionally skipping the parameter configuration step when the selected tool does not require additional parameters. It achieves this by checking the presence of properties in the tool's schema and updating navigation logic and button labels accordingly. The changes affect both converter and explorer creation flows for a more intuitive user experience.
Conditional step navigation and workflow improvements:
ConfigureToolModal.jsxare now dynamically set: if the tool's schema has properties, both "Configure Scope" and "Configure Parameters" steps are shown; otherwise, only "Configure Scope" is presented.FormConverterSection.jsx,FormExplorerSection.jsx), the navigation after the scope step is updated: if no parameters are required, the process skips directly to saving the tool; otherwise, it proceeds to the parameter configuration step. [1] [2]Component interface and button label updates:
ScopeStepConverter.jsxandScopeStepExplorer.jsxcomponents now receive anextStepcallback instead ofsetStep, allowing conditional navigation logic. [1] [2]Before

After
