* feat: add nodejs generator
Signed-off-by: Michael Beemer <michael.beemer@dynatrace.com>
* feat: add a nodejs generator
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
* improve doc diff output
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
* check out expected sha
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
* fix variable name
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
* feat: consolidate logging and support debug flag
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
* regenerate docs
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
---------
Signed-off-by: Michael Beemer <michael.beemer@dynatrace.com>
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
closes#87
## This PR
This update introduces the addition of stability information to the
generated markdown content for commands in our CLI. The changes include
a new function, `addStabilityToMarkdown`, which checks if a command has
a 'stability' annotation and adds it to the markdown content
accordingly. This function is then used in both `generate.go` and
`init.go`. Additionally, formatting adjustments were made in `root.go`
for better readability.
### Notes
- Some of the logic felt a bit astonishing, so I left a lot of comments.
If this isn't helpful, I'd be happy to remove them.
- I tried to approach this in a way where the addedStabilityInfo was
inherent and not imperative.
- There is still one imperative func that needs to be used in each
command, I would be open to suggestions to eliminate it.
- The logic for customizing the markdown should work for any command we
implement in the future.
- I was going to try and use go templating to achieve this, but ended up
going with a 'mutate after the fact' approach.
- This approach could be utilized in the future to customize the docs
further, but the logic to do so is very procedural. In the future, I
would like to think up a more declarative approach, I think this could
improve it so it's more easily extensible and less to maintain.
### Follow-up Tasks
- Possibly introduce a more declarative approach so we can extend
markdown customization more easily in the future, without having to
write additional logic to figure out where to place the custom content.
### How to test
- [ ] run `make generate-docs` and you should see the stability info
output in the docs. Change or add a new stability info to a command, try
it, and you should see the changes updated.
Signed-off-by: Kris Coleman <kriscodeman@gmail.com>
## This PR
- moves JSON schema to a dedicated directory
- added schema validation tests
- fixed React code gen (and tests)
- automate CLI doc generation
- Loosen JSON schema
- ~~Rename default value~~
### Related Issues
Fixes#66
### Notes
It's a big PR that I could break into smaller changes if necessary.
---------
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
Signed-off-by: Michael Beemer <michael.beemer@dynatrace.com>
Michael Beemer