Add None provider, path expansion, refactoring #251
Merged
Conversation
This file contains 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
- Add None provider and protocol for solely creating network-ready network namespace with no VPN service - Add shell path expansion to path arguments (e.g. you can use ~ in custom config path) - Refactor how CLI arguments are parsed using macro_rules
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.
Add None provider and protocol for solely creating network-ready network namespace with no VPN service
Add shell path expansion to path arguments (e.g. you can use ~ in custom config path)
Refactor how CLI arguments are parsed using macro_rules
Now all CLI args except
applicationcan be set in the vopono config TOML too