- Depends On:
Simplify the buffers by making everything work on a TalkatuBuffer
Review Request #2224 — Created Jan. 31, 2023 and submitted
The only things the content type specific buffers were doing now as defining which formatting actions would be enabled. So we now created an flags and a property on TalkatuActionGroup to fix that. By doing so, we are able to get rid of TalkatuHTMLBuffer, TalkatuMarkdownBuffer, and TalkatuWholeBuffer.
Ran the demo, tested all the buffers as well as the insert html and mark down actions.
Summary | ID |
---|---|
feaa3f7b8dd3a6291e4af02f48fea97242c8d021 |
Description | From | Last Updated |
---|---|---|
It's just name in the function header. |
ivanhoe | |
s/not enable/to enable |
ivanhoe | |
*its |
ivanhoe | |
s/action_name/name |
ivanhoe | |
Should there be a notification about the changed buffer? |
ivanhoe | |
*currently |
ivanhoe | |
*currently |
ivanhoe | |
It still says TalkatuMarkdownBuffer in the comment. |
ivanhoe | |
Shouldn't this documentation go into the header, since it's public API? |
ivanhoe | |
*TalkatuBuffer |
ivanhoe |
- Change Summary:
-
rebased
- Commits:
-
Summary ID b663e39cbe99560952a674645482e2ec1731d151 df5c478b12de9cd16a694ce5fda34dfe5ef39aab
- Change Summary:
-
addressed issues.
- Commits:
-
Summary ID df5c478b12de9cd16a694ce5fda34dfe5ef39aab 346fe3a1470e162502b66758bd3e9d89ea9fed45