fix: remove commented-out base path referencing old project name#164
Open
vanshaj2023 wants to merge 1 commit into
Open
fix: remove commented-out base path referencing old project name#164vanshaj2023 wants to merge 1 commit into
vanshaj2023 wants to merge 1 commit into
Conversation
jagpreetrahi
approved these changes
Mar 20, 2026
Collaborator
|
@AgniveshChaubey , ready to merge |
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
2 participants
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
Removes a commented-out
basepath invite.config.tsthat referenced the old project name/visualize-json-schema/. This line was leftover from a previous rename and serves no purpose.What kind of change does this PR introduce
Code cleanup removes dead commented-out code.
Issue Number
Closes #163
Screenshots/Video
Not applicable because no UI changes.
Does this PR introduce a breaking change?
No.
If relevant, did you update the documentation?
No.