-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When will 1.0 be ready? #226
Comments
Another day, another dozen squashed bugs. Most notably we included better customization for those wanting to do their own cmdtree text implementations while allowing the mark.Usage to be completed. cmds/help got a rebuild making it ready for inclusion in other tools. We also added Cmd.Def back when other use cases emerged that make it extremely valuable and not necessarily tied to Cmds. |
Add Cmd.Env to assist with setting environment variables in a way that does not depend on the shell. All will be set in the Seek path. |
... and now we have SeekInit and Cmd.Init which provides powerful insight possibilities when descending into the command to be run. |
Moved Vars and Env to bonzai.VarMap so easier to write. |
Reworked |
Just knocked out one of the more complicated things remaining before a 1.0, variable declaration, inheritance, and persistence. |
In case you are wondering where all the beginner documentation has gone (including the book that was started), everything is archived until v1.0 is released.
Here are the modules that (at least) must be v1.0.0 before we can consider Bonzai itself at v1.0.0:
cmds/help
comp
cmds/vars
cmds/vars/cmd/var
Before they get that tag must have following:
go cover
We will also need an approved logo before I'll put a v1.0.0 on anything.
The text was updated successfully, but these errors were encountered: