Fix workato init to detect existing projects after user selection #23
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.
Summary
Fixed the project detection logic in
workato initto check for existing projects AFTER the user selects which project they want to initialize, rather than prematurely prompting based on any.workatoenvin the current directory.Problem
The old behavior would check for any
.workatoenvfile in the current directory BEFORE the user selected which project they wanted to initialize. This caused confusion when users had old project files from previous initializations that were unrelated to what they wanted to initialize.Solution
.workatoenvbefore user selection_find_all_projects()project_idacross entire workspaceChanges Made
Files Modified
src/workato_platform/cli/utils/config/manager.py_setup_project())_find_all_projects()and matches byproject_idtests/unit/config/test_manager.pyTest Coverage
Added comprehensive test coverage (6 new tests):
Test Results: All 899 tests passing
Quality Checks
✅ All type checks pass (mypy)
✅ All linter checks pass (ruff)
✅ Code properly formatted
✅ 96% test coverage on modified code
✅ All 899 tests passing
🤖 Generated with Claude Code