vab, cli: refactor flag parsing, deprecate programmatic flag.FlagParser
usage
#294
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.
This PR refactor flag handling in
vab
andvab.cli
to be a bit more ergonomic to work with. The existingflag.FlagParser
functionality is preserved, but deprecated.This is the first step in simplifying the way
vab
works internally (and programmatically viavab.xyz
usage).The plan going forward is to allow for easier extending/reusing
vab
's powerful functionality in user space.I hope to bring support for user space supplied commands that can be installed and run via
vab
itself to allow for extendingvab
's support for user space projects.And example of such a user space command, could be a command that brings
vlang/sdl
support tovab
via e.g.:vab sdl --archs arm64-v8a run ~/.vmodules/sdl/examples/basic_window
the same could then be done for e.g. variousraylib
wrappers etc.