1.0 Roadmap

[NoNameProvided]

There are quite a few things we should fix/implement before releasing 1.0, some of these will be a breaking change.

Note: this issue will be updated as progress is made towards these goals.

• Features
  • adding ValidationError.toString() (ValidatidationError .toString()  #26)
  • experimenting to see if we can add support for class method validation (Can we validate arguments going into class methods? #115)
  • rethink how groups are handled
  • experimenting to see if we can add support for dynaimc constraints (feature: allow passing dynamic constraints to the validate function #76)
  • add validation modes (fail on first error) (Feature request: Fail on first ValidationError. #148)
  • support i18n for error message (How to customize validation messages globally? #169)
  • rething the structure of the error object for easier usage
  • add some low level decorator for runtime logic, GreaterThan and GreaterOrEquals decorator or a more generic one what expects a property key and a compareFn function.
• Schema based validation (schema based validation will be deprecatated)
  • fix current bugs
  • add test coverage
  • make every validator available
  • add option to generate JSON schema from class metadata
  • add support of registering validation schema for target class
  • add support of registering custom validations without using decorators
  • add support for serializing metadata and importing it (so registered metadata can be transferred over the network)
• Documentation
  • split up docs into sections
  • add a documentation site
  • add documentation for usage with pure JS
  • add documentation for usage with babel + decorators
  • add documentation about using error output with Angular's Reactive Forms module (Example for use this awesome module in angular 2 form validation.  #69)
  • add better docs about custom decorators and validation classes
• Project setup refactor
  • split up files, better code oraganziation
  • add Prettier for code formatting
  • add husky for auto formatting and running tests before commits
• Test setup refactor
  • move to Jest (batteries included and out-of-box TS support)
  • split test files and move them next to the components they test

---

Please do not comment things like "+1" or "Me too", but feel free to add your voice.

[lucasmonstrox]

Awesome. Waiting for rethink how groups are handled MUAHAHAHA :D Love u guys.

[yantrab]

about (#69)
this is how i do it.

[dsbert]

It is not encouraging that in two years, only one checkbox has been checked on this list and the project is still on version 0.11.0 (released 15 months ago).

[glen-84]

@NoNameProvided,

add validation modes (fail on first error) (#148)

Is this resolved by #620?

add Prettier for code formatting

This is done.

[ytetsuro]

@NoNameProvided

add validation modes (fail on first error)

This is fixed.

[yitzchak-ben-ezra-ecoplant]

This repo is DEAD.. no ones (except bot) maintains it..
I think you should allow more users to maintain it.. approve PRs etc...

[armingjazi]

@NoNameProvided Is there any long term plan to maintain this repo? Would you consider transferring the ownership?

[hood]

@NoNameProvided and @pleerock do you have any plans on including more people as maintainers for this project? This is getting ridiculous. There is still a lot of work to be done on this repository, and keeping this situation stale is not going to help in any way. Please don't let this end up like TypeORM did.

[kasir-barati]

@NoNameProvided please fix this issue. it is a very annoying and discussing error. i am tired, because of the whitelist I force to copy and paste my code multiple places and this is a very bad practice.

#1288