Releases: fpm-git/gabagool
Gabagool v0.0.6
This patch introduce a bug-fix and support for a couple new features.
Fixes:
- Certain types of JSDoc Promise parameter/return type definitions will no longer result in a crash. Specifically, the bug affected Promise definitions where a union type was used for the resolved value (for example:
Promise<any|any[]>).
New features:
- There now exists support for rest parameters, where they used to be excluded from the parameter set.
- The Sails v1
customToJSONmodel method is now supported. If this method is defined on any model, it will be excluded from the static definition, and instead added to the instance definition astoJSON?(...).
Gabagool v0.0.5
This patch changes the behaviour where importing hooks as dependencies in a normal project would throw an error, claiming that said dependencies should be moved into devDependencies instead.
Now, only hooks importing other hooks will receive this error. Yeay!
Gabagool v0.0.4
This release includes improvements to typing for Waterline method parameters (find, findOne, create, update, etc. all have suitable model types generate for their criteria/instance values).
Also included is a fix for certain import scenarios, which makes custom function parameter types behave as they should, all the time.
Gabagool v0.0.3
There are quite a few gabagoodies in this release, compared to v0.0.2, and especially over v0.0.1.
Improvements over v0.0.2 include:
- Proper autocomplete support for parameters in function definition bodies, or any other JSDoc-typed variable. (Function calls already worked, but this takes typing to the next step; allowing for comfort everywhere, not just when calling a model function).
- Cleaner model output (through export/import vs. inlining)
- No more lifecycle callback definitions generated. These shouldn't ever be manually invoked, and so just ended up taking a bit of precious autocomplete space, no more!
If still on v0.0.1, I urge you to upgrade, as v0.0.2 included a few really great improvements, including:
- Autocomplete for req/res parameters (through
SailsRequest/SailsResponseglobal definitions). - Recognition for certain promise return values which previously evaded the parser.
- Much cleaner output, from a fix to the import generator process.
While 0.0.1 will continue to function without error, it is suggested to use at least 0.0.3, for team-consistency with type annotations, which are not anticipated to change after this point.