Roadmap
See original GitHub issueRoadmap
Github Issues
- Investigate all issues, tag and label by type (in progress)
- Close none relevant or outdated ones (in progress)
- Note the major bugs and issues and tackle those first
- Outline biggest missing features of current version and see if workaround is possible (like error extractor)
Documentation Related
- Transfer docs to Vuepress for easier contribution (in progress)
- Update docs to answer most common questions
- Add a whole section with recipes and examples
- Add a whole section explaining concepts and architecture
Package Progression Forward
v2
Alpha released!
- Outline the new, most important features
- Outline secondary features, that are not of most importance
- Create official form handling, accompanying library for Vuelidate (https://github.com/vuelidate/formvuelatte)
- Complete Rewrite
- Using TypeScript (on hold)
- Simplify the codebase to make it easier to contribute code
- After initial attempts to rewrite it using Vue.observable, we decided to hold on the rewrite, due the fact that Vue 3.0 will most likely introduce the Advanced Reactivity API, which in turn would hugely simplify the internal implementation of Vuelidate. For example, it would allow us to stop creating Vue component instances on the fly to manage internal validation state. Rewritten using the composition-api plugin
- Docs (in progress)
- Migration guide (on hold)
Major Changes in v2:
- CHANGE: Extract validators to external package or leverage another package entirely
- NEW: Add first party error extraction logic with proper defaults. Should allow for scoped slots or instance method helpers
- NEW: Add better async validator support
- NEW: Allow validators to return extra data, not just booleans.
- NEW: Give parent components access to all child components validation results. This should allow for breaking up the validation schema and building nested forms with one central parent component that can decide on the actions.
- IDEA: Remove the
$each
API-
Use map/reduce to validate arrays.NEW: Introduceevery/some
helpers.
-
Issue Analytics
- State:
- Created 4 years ago
- Reactions:12
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Developer Roadmaps
Community driven roadmaps, articles, guides, quizzes, tips and resources for developers to learn from, identify their career paths, know what they don't ...
Read more >What is a roadmap? - The ultimate guide to ...
A visual roadmap is a communication tool. They're created and presented to get all stakeholders, executives and your entire team aligned on one...
Read more >Roadmap Basics
A roadmap is a strategic plan that defines a goal or desired outcome and includes the major steps or milestones needed to reach...
Read more >Roadmapping: Your starter guide
A roadmap is a visual representation of your strategic plans. It ties together your strategy (the "why"), the work you will need to...
Read more >Roadmap
A road map, a form of map that details roads and transport links · A plan, e.g.. Road map for peace, to resolve...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey! v2 is still in the making. It will stay that way up until Vue 3.0 is released due to the fact it is dedicated to Vue 3.0, with a compatibility layer using the composition-api plugin for Vue 2.x.
You can check out the progress on the
next
branch. It is already released as an alpha, though it’s rather buggy. We are currently working on solving some issues with the compatibility with the current Object-based API as well as exploring ideas on how to build context-aware validations. That is, components with validations reporting to ancestor components with validations so that you can split the validator declarations between different components, yet still have an easy way to access the results (with built-in messages).Here’s a presentation I made that touches heavily on what we have planned for Vuelidate (and also FormVueLatte). When it comes to an ETA – I plan on doing having most of those things done around mind February.
https://github.com/shentao/vue-3-for-library-authors/blob/master/vue-3-library-authors-january-update.pdf
Also sorry for the radio silence – I’m personally quite a bit overwhelmed with all the things around developing a library and I simply forgot to update the issue. As they say – writing the code is the easy part.
Updated the initial post here. 😃
I second the comments made above, were looking for feeback from the repo owners here;