-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration from Dataview to Datacore #5
Comments
All metadata formats are still supported. Dataview blocks can be translated to datacore editable blocks automatically. I haven't decided on DataviewJS yet, since the changes there are more substantial. The easiest route may just be to provide a legacy API layer so existing scripts continue to run, since an automatic rewrite tool is unlikely to be feasible. |
The other option I'm considering is simply rewriting dataview to use datacore internally, and you keep dataview installed to support any dataview/dataviewjs blocks. |
that would be a need option too. I don't have too much dataviewjs code inside my nodes, most of it is externally, so easy to change. the normal dataview blocks are a lot though, especially in my journaling. Looking forward to it. |
Have a mixture of dataviewjs and dataview, but I am more incline to switching to datacore if it is better and easier to maintain. |
hey, on the question of dvjs. will the new js api still be usable by templater and the other plugins that use dvjs as code basis? |
Any plans on how people will migrate from dataview to datacore?
I heavily use dataview in my journaling, manually editing all daily, weekly, monthly, quarterly and yearly notes would be... quite a task.
And that is only one example where an automated / semiautomated way of migration would be helpful.
I know that this will not work for dataviewjs (either in note or in other javascript). But here a good "How-To move from Dataview to Datacore JS / API" could help.
So it would be nice to see what you have planned for this on your roadmap.
The text was updated successfully, but these errors were encountered: