-
Notifications
You must be signed in to change notification settings - Fork 486
Too many parameters bug #554
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
Comments
Thanks for the report! We're sorting parameters based on order in the source, but that sorting wasn't sensitive to nested parameters. 58c6892 should fix this issue by only sorting auto-detected parameters and inserting them just at the point where they're needed, before any nested params. |
thanks a lot! |
tmcw
added a commit
that referenced
this issue
Apr 15, 2017
This nesting implementation uses a proper recursive tree algorithm Fixes #554
2 tasks
tmcw
added a commit
that referenced
this issue
Apr 15, 2017
This nesting implementation uses a proper recursive tree algorithm Fixes #554
tmcw
added a commit
that referenced
this issue
Apr 15, 2017
This nesting implementation uses a proper recursive tree algorithm Fixes #554
tmcw
added a commit
that referenced
this issue
Apr 15, 2017
This nesting implementation uses a proper recursive tree algorithm Fixes #554
tmcw
added a commit
that referenced
this issue
Apr 15, 2017
This nesting implementation uses a proper recursive tree algorithm Fixes #554
tmcw
added a commit
that referenced
this issue
Apr 15, 2017
This nesting implementation uses a proper recursive tree algorithm Fixes #554
tmcw
added a commit
that referenced
this issue
Apr 15, 2017
This nesting implementation uses a proper recursive tree algorithm Fixes #554 BREAKING CHANGE: referencing inferred destructure params without renaming them, like $0.x, from JSDoc comments will no longer work. To reference them, instead add a param tag to name the destructuring param, and then refer to members of that name. Before: ```js /** * @param {number} $0.x a member of x */ function a({ x }) {} ``` After: ```js /** * @param {Object} options * @param {number} options.x a member of x */ function a({ x }) {} ```
tmcw
added a commit
that referenced
this issue
Apr 15, 2017
This nesting implementation uses a proper recursive tree algorithm Fixes #554 BREAKING CHANGE: referencing inferred destructure params without renaming them, like $0.x, from JSDoc comments will no longer work. To reference them, instead add a param tag to name the destructuring param, and then refer to members of that name. Before: ```js /** * @param {number} $0.x a member of x */ function a({ x }) {} ``` After: ```js /** * @param {Object} options * @param {number} options.x a member of x */ function a({ x }) {} ```
tmcw
added a commit
that referenced
this issue
Apr 15, 2017
This nesting implementation uses a proper recursive tree algorithm Fixes #554 BREAKING CHANGE: referencing inferred destructure params without renaming them, like $0.x, from JSDoc comments will no longer work. To reference them, instead add a param tag to name the destructuring param, and then refer to members of that name. Before: ```js /** * @param {number} $0.x a member of x */ function a({ x }) {} ``` After: ```js /** * @param {Object} options * @param {number} options.x a member of x */ function a({ x }) {} ```
tmcw
added a commit
that referenced
this issue
Apr 15, 2017
This nesting implementation uses a proper recursive tree algorithm Fixes #554 BREAKING CHANGE: referencing inferred destructure params without renaming them, like $0.x, from JSDoc comments will no longer work. To reference them, instead add a param tag to name the destructuring param, and then refer to members of that name. Before: ```js /** * @param {number} $0.x a member of x */ function a({ x }) {} ``` After: ```js /** * @param {Object} options * @param {number} options.x a member of x */ function a({ x }) {} ```
tmcw
added a commit
that referenced
this issue
Apr 21, 2017
* refactor(nest): Better nesting implementation This nesting implementation uses a proper recursive tree algorithm Fixes #554 BREAKING CHANGE: referencing inferred destructure params without renaming them, like $0.x, from JSDoc comments will no longer work. To reference them, instead add a param tag to name the destructuring param, and then refer to members of that name. Before: ```js /** * @param {number} $0.x a member of x */ function a({ x }) {} ``` After: ```js /** * @param {Object} options * @param {number} options.x a member of x */ function a({ x }) {} ``` * Address review comments * Reduce testing node requirement back down to 4 * Don't output empty properties, reduce diff noise * Rearrange and document params * Simplify param inference, update test fixtures. This is focused around Array destructuring: documenting destructured array elements with indices instead of names, because the names are purely internal details * Use temporary fork to get through blocker
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, we have the following code documentation:
This is rendering this way:
As you can see it changes the order of the parameters in the function, the last option it's rendered as a parameter and the
yIn
goes to the bottom.The generated JSON seems correct and with less arguments behaves as good as before (remove until
maxCriteria
and works fine again).The text was updated successfully, but these errors were encountered: