Fix Consolidate repo_name and repo_path into a Single Repository Identifier #523
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.



Status Report: Issue #517 & Local Development Setup
1. Completed Changes
I have successfully refactored the codebase to consolidate
repo_nameandrepo_pathinto a singlerepository_identifier, allowing the system to intelligently distinguish between local paths and remote GitHub repositories.Backend Changes
RepoResolverclass (app/modules/parsing/graph_construction/repo_resolver.py) to handle repository identification logic.ParsingRequestinparsing_schema.pyto replacerepo_name/repo_pathwithrepository_identifier.ParsingControllerto useRepoResolverfor early validation and resolution of repository details.ParsingServiceandParseHelperto work with the newRepoDetailsobject, streamlining the logic for local vs. remote cloning.RepoDetailsfrom serialized data.ProjectServiceto handle optional fields and ensure correct type handling (string vs int for project IDs).Frontend Changes
BranchAndRepositoryService.tsto send the newrepository_identifierpayload to the backend.Bug Fixes
auth_service.py(removed@classmethodfromcheck_authwhich was causing startup errors).2. Current Status & Known Issues
The core refactoring is complete and the backend server starts successfully. However, I am currently facing issues with the local development experience when trying to select a repository in the UI.
Active Issues
Repository Selection Error:
/api/v1/github/user-reposendpoint attempts to authenticate with GitHub. In my local environment (without a GitHub token), this raises an exception, causing the 500 error.Local Path Input:
D:\Webdev\Open Source\potpiedirectly.3. Work in Progress / Next Steps
To fully resolve the local setup and allow me to test the parsing feature, I need to address the environment and UI limitations:
Fix Repository Listing Endpoint:
github_router.pyto gracefully handle authentication failures indevelopmentmode. Instead of crashing, it should return a default/empty list or demo repos.Enable Custom Path Input in UI:
AgentCreationChatPanel.tsxto allow users to type a custom string (local path) and select it, bypassing the requirement for it to exist in the GitHub list.Environment Configuration:
CODE_PROVIDER_TOKENorGH_TOKEN_LISTcan be added to.envto enable actual GitHub connectivity if desired, though the local path fix (step 2) is the priority for my use case.