Skip to content
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

fix: Improve fig spec with better generators #3762

Open
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

miguelmig
Copy link
Contributor

Also prevents some issues that might trigger the autocomplete's linter.
This, together with the changes on usage-cli 1.7.3 version, should get the automated PR to pass the linter checks on the autocomplete repo

@miguelmig miguelmig changed the title Improve fig spec with better generators bugfix: Improve fig spec with better generators Dec 21, 2024
@miguelmig miguelmig changed the title bugfix: Improve fig spec with better generators fix: Improve fig spec with better generators Dec 21, 2024
@miguelmig
Copy link
Contributor Author

There's still one nasty eslint complaint about descriptions that I can't get to popup on this repo, still struggling with figuring out how eslint imports rules from other modules..once I figure it out I'll leave a comment here.

@jdx jdx marked this pull request as draft December 21, 2024 15:35
@miguelmig miguelmig marked this pull request as ready for review December 23, 2024 18:10
@@ -264,7 +264,7 @@ function cliReference(commands: { [key: string]: Command }) {
x.collapsed = true;
x.items = Object.keys(command.subcommands)
.filter(
(subcommand) => command.subcommands![subcommand].hide !== true,
(subcommand) => command.subcommands![subcommand].hide !== true
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer if we didn't need to enable es5 style everywhere

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair point, will investigate if I can use package.json hierarchy to handle this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants