Skip to content

Releases: mrjono1/joi-to-typescript

2.4.0

11 Jan 06:58
3ec7948
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 2.3.0...2.4.0

2.3.0

22 Nov 10:21
c9a7ffd
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 2.2.2...2.3.0

2.2.2

27 Sep 11:44
5d7cf4f
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.2.1...2.2.2

2.2.1

09 Sep 08:42
bedca41
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.2.0...2.2.1

2.2.0

09 Sep 07:32
a479168
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 2.1.1...2.2.0

2.1.1

01 Sep 09:59
8b68919
Compare
Choose a tag to compare

What's Changed

Full Changelog: 2.1.0...2.1.1

2.1.0

07 Jul 10:01
ad38bee
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 2.0.2...2.1.0

2.0.2

02 Jul 10:24
760858f
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 2.0.1...2.0.2

2.0.1

20 Jun 11:36
c99538a
Compare
Choose a tag to compare

What's Changed

  • updated imports they work locally but not as deployed npm package by @mrjono1 in #108

Full Changelog: 2.0.0...2.0.1

2.0.0

20 Jun 11:10
13a96a5
Compare
Choose a tag to compare

Version 2
Changing interface name setting to .meta({className:'') from .label('')

Why the move to .meta({className:'') from .label('')? Joi.label() is intended to be used for meaningful error message, using it for another purpose makes the Joi loose a standard feature, this is especially noticeable for frontend usages of Joi. The choice of the property className is because this property is used by joi-to-swagger, making this project work with other projects is important.

Upgrade Notice
Version 1 used .label('Person') as the way to define the interface name, to continue to use this option set { useLabelAsInterfaceName: true }

What's Changed

Full Changelog: 1.14.1...2.0.0