Releases: ezzatron/austenite
Releases · ezzatron/austenite
v0.10.1
Fixed
- Removed unused
mdast
dependency.
v0.10.0
Added
- Custom constraints can now be defined for all declarations.
Changed
- [BREAKING] The
initialize()
function is nowasync
. - If you have Prettier installed in your project, Austenite will now use it to format generated Markdown specification output.
- The generated specification output has been improved.
- Markdown phrasing content is now supported in variable and constraint descriptions.
v0.9.1
Fixed
- Replaced usage of
node:
imports to avoid issues when Austenite is included in a Webpack server bundle.
v0.9.0
Added
- Example values can now be overridden in any declaration.
Changed
- [BREAKING] Explicit examples must be provided in a declaration if the declaration uses constraints that would make the auto-generated examples invalid.
v0.8.0
Added
- Declarations can now be marked as sensitive, which will cause their default values and actual values to be redacted in validation summaries, generated specifications, and exception messages.
- Length constraints can now be set on
binary
andstring
variable declarations. - Range constraints can now be set on
number
,integer
,bigInteger
,networkPortNumber
, andduration
variable declarations.
Changed
- The generated specification output has been improved to be easier to read.
- The validation summary output uses "not set" instead of "undefined" to describe values that are not set, or are set to empty values.
v0.7.0
Added
- Added
binary
variable declarations.
v0.6.2
Fixed
- Fixed badge images and links in the README.
v0.6.1
Fixed
- Fixed CJS TypeScript build.
v0.6.0
Changed
- Renamed the NPM package from
@eloquent/austenite
toaustenite
.
v0.5.0
Added
- Added
networkPortNumber
declarations.