-
Notifications
You must be signed in to change notification settings - Fork 41
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
Feature request: Storing documents on a local environment option (no Firebase) #126
Comments
You can delete whole documents under the version list (see screenshot above). Is that what you want? (Or do you mean deleting individual versions? That's not available yet but you can run clean DB under Manage Database in the browser, which will reduce all documents to 65 versions max. If you'd like to be able to delete specific versions let me know.) |
Oh sorry sorry sorry! I forgot was running Parseq not on 3000 last couple of days (3000 used for other day to day dev env's) So suddenly all my template dos disappeared from the Load New option and surely under Sorry silly mistake. About the delete, yes would be nice to be able removing a document directly from the UI. |
No probs! If you want to move all your documents between localhost:3000 and the prod site, you can got to Browser / Manage Database – you'll find import/export functions there. |
Yes :) used this already. What do you think about the delete per doc feature? |
Easier access to deleting docs and deleting specific doc versions are both good ideas! |
Adding on option to save the document with a custom name locally.
From what I saw at the moment (using v0.1.57) you are storing
in
indexDB
the current document and you can access you older onesonly with
Revert
in the UI which is basically pullingfrom
parseqVersions
underparseqDocs
.Would be nice if there would be a button for
Save
orSave Local
that would add the documentin a new entry under
parseqDocs
So you could manage your docs with names instead of using
Revert
Also adding a
Delete
button again helping you managing better your docs.For me personally I prefer using it locally and I don't need thousends of document.
The way I'm using Parseq is testing around until Im satisfied with the document result
then re using it over and over using the initial template.
Opened an issue as a request but would gladly do it myself.
Just wanted to check if this is a desired direction before start
working on a PR
As commented on Youtube, This project is incredible
Brilliant work
The text was updated successfully, but these errors were encountered: