Skip to content

Making flags validation more strict and disallow unknown flags

Compare
Choose a tag to compare
@thetutlage thetutlage released this 23 Apr 12:31

The release has a breaking change, since the flags are more strict and we disallow all the known flags when running a command.

Earlier, the value for the boolean was to false and for a string flag was set to an empty string by default, even when the flag was not mentioned. Now, it is set as undefined. The change is made to distinguish between the user define values and the implicit defaults.

Also, the boolean flag no longer going to accept non boolean values anymore.

Commits

  • docs(README): update links 4a7795f
  • refactor: making flags more strict and dropping default,defaultValue options f6d565b
  • improvement: force property using args decorators to have correct types dac52d3
  • improvement: do not accept "propertyName" and "type" via decorators f89afe7
  • chore: update dependencies af68f40

v10.0.1...v11.0.0