I would be here on Friday, so in regards to @phillipskevin’s topic I think we should poll the community and clients to see versions they are using and how flexible they are about being able to upgrade.
I’ve been working on can-validate recently. Specifically, a refactor based on this proposal.
I’d like to discuss a couple things:
can-validate-legacy (3.0 compatible version of what can-validate is now)
can-validate suite
The plan is to break out can-validate into parts, following the pattern we’re using with other 3.0 projects. Those parts would consist of…
DefineMap plugin
Our own validation library
ValidateJS library plugin
This might be a lot to talk about so, if we need to focus on one topic, I think how we are handling the different “versions” was a hot topic last time.
can-validate-legacy: currently a pre-release; docs should be available soon
can-validate: break it up into smaller modules
Proposal options
– option 1: more explicit APIs you have to learn about
– option 2: simplified APIs; lose flexibility of different validators, but that doesn’t seem like a worthwhile goal
It’d be great to make this module usable with the decorators syntax
We need to expose more of the DefineMap internals for can-define-stream and can-define-validate
– Need to figure out hooks that could be used for both of them
DoneJS 1.0 supported Node.js versions:
We’ll poll the community to see which versions are being used
Idea: support the same versions that are maintained by the Node.js community
– Node.js LTS schedule
Node.js v4 should be easy to support; only missing out on ES6 features