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
Allow Buffers to have types by introducing a new event type:
dataBufTypeChangedbufType=BufTypeChanged
BufTypeChanged ReadOnlyBuffer for read-only buffers in rasa-ext-files (rasa -R example.txt) BufTypeChanged (EditorBuffer languageType) for specifying syntax choice in rasa-ext-syntax. Allowing to make syntax modular by having for instance a markdown syntax extension listen to BufferTypeChanged (EditorBuffer MarkdownLanguage) BufTypeChanged FileBrowser for a file browser, etc.
The text was updated successfully, but these errors were encountered:
Should the BufTypeChanged type be introduced in Rasa.Internal.Events or in an extension?
Should BufAdded be extended also to include the BufType in addition to the BufRef?
Yes, I think that makes sense for both of those. The tricky bit will be how to standardize buffer types across all extensions? We can either add some common ones into the core, or we can write a simple module that just has 'all' the filetypes in it and people can add new ones as needed 😄
cc @jmatsushita
Allow Buffers to have types by introducing a new event type:
BufTypeChanged ReadOnlyBuffer
for read-only buffers in rasa-ext-files (rasa -R example.txt)BufTypeChanged (EditorBuffer languageType)
for specifying syntax choice in rasa-ext-syntax. Allowing to make syntax modular by having for instance a markdown syntax extension listen toBufferTypeChanged (EditorBuffer MarkdownLanguage)
BufTypeChanged FileBrowser
for a file browser, etc.The text was updated successfully, but these errors were encountered: