You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This is a safety feature. It is yet have to be confirmed, but I think that, when you delete a obsidian plugin, the plugin folder (including its settings) gets deleted. This means that all the user form definitions will be lost.
Some people may like this, but some other people will prefer the ability to delete a plugin, keep their configs and be able to install it again without loosing any data.
Describe the solution you'd like
The plugin should ask for a "forms folder", similar to what templater does for templates and many other plugins do. Then load all the files in that folder and try to parse forms from them.
This introduces some complexity, so I'm not in a hurry to implement this, but I want to keep track of it anyway.
Also, this probably should be a configuration option, to enable or disable it.
Ideally, when you enable it user may choose to export all their forms to the folder.
Additional context
This introduces some complexity as I mentioned, that I will list here:
what should be the format? markdown with JSON sections? or just JSON files.
Should we use exclusively one source? or should we try to load from both?
Migrations will become slightly harder because people may change the files themselves (as they will be more visible), so probably a bit of more robust error handling is required.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
This is a safety feature. It is yet have to be confirmed, but I think that, when you delete a obsidian plugin, the plugin folder (including its settings) gets deleted. This means that all the user form definitions will be lost.
Some people may like this, but some other people will prefer the ability to delete a plugin, keep their configs and be able to install it again without loosing any data.
Describe the solution you'd like
The plugin should ask for a "forms folder", similar to what templater does for templates and many other plugins do. Then load all the files in that folder and try to parse forms from them.
This introduces some complexity, so I'm not in a hurry to implement this, but I want to keep track of it anyway.
Also, this probably should be a configuration option, to enable or disable it.
Ideally, when you enable it user may choose to export all their forms to the folder.
Additional context
This introduces some complexity as I mentioned, that I will list here:
The text was updated successfully, but these errors were encountered: