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
Because of some problems with the conversion "Visual editor" < - > "Markdown" ("Texitle"?) in both directions now (see, for example, #90) and perhaps in the future, I think it will be useful to add the "Don't use Visual editor" option to each Formatted text row (the default behavior is in the plugin settings in the Redmine admin panel).
Thus, this option will allow you to keep the old formatted text undamaged when bugs are reported and for the fixing period.
Moreover the plugin will be production-ready. What do I mean? The plugin is already ready for 90% of usage cases. But it's cool when you don't think about rendering result every time you edit the complex text (just set the option and edit in the "raw" mode).
The text was updated successfully, but these errors were encountered:
For discuss.
Because of some problems with the conversion "Visual editor" < - > "Markdown" ("Texitle"?) in both directions now (see, for example, #90) and perhaps in the future, I think it will be useful to add the "Don't use Visual editor" option to each Formatted text row (the default behavior is in the plugin settings in the Redmine admin panel).
Thus, this option will allow you to keep the old formatted text undamaged when bugs are reported and for the fixing period.
Moreover the plugin will be production-ready. What do I mean? The plugin is already ready for 90% of usage cases. But it's cool when you don't think about rendering result every time you edit the complex text (just set the option and edit in the "raw" mode).
The text was updated successfully, but these errors were encountered: