Fixes #15: config2vmess: Parsing the correct address and port from config files#18
Open
AliSawari wants to merge 4 commits into
Open
Fixes #15: config2vmess: Parsing the correct address and port from config files#18AliSawari wants to merge 4 commits into
AliSawari wants to merge 4 commits into
Conversation
This was referenced Nov 8, 2024
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.
Fixes #15, #13
the command
config2vmesswas previously reading theaddressandportfrom thetagproperty in the outbound item object, which was resulting into the error mentioned in the linked issue. it is now parsing the correct data from thevnextitem object, which contains the actual data for theaddressandport.Additionaly this PR also included an example config.json for a correct vmess config file for testing purposes. located in
config-examplesfolderChanges:
obj?.prop) to remove thecannot read prop of undefinederrorspnpm-lock.jsonto gitignore, because there's an already existing lock file for npm.