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
So right now this plugin works by inserting real code into your text editor. This is basically inherited from the implementation in modeling-app. The pro of this is that the 'ghost text' gets proper syntax coloring and behaves like real code. The con is that when we insert ghost text, it generates real change events, so the actual code in the editor changes when you have ghost text displayed. So you can get into situations like:
You're editing some text
You end a line of text with something
Codeium feels like it has a good suggestion to show you
The suggestion is displayed briefly
You close the tab
When you re-open the tab, the ghost text is shown as "unsaved changes that were recovered" (if you have a recovery system)
This is obviously less than ideal, and ends up with (in our case) having a method exposed like shouldTakeUpdate which lets upstream systems ignore change events. But the whole necessity of that shouldTakeUpdate method is driven just by the fact that ghost text is, surprisingly, real code in your editor.
The text was updated successfully, but these errors were encountered:
Having slept on it, realizing that the extra benefit of the current system is that it works smoothly with multi-line insertions and decorations probably wouldn't.
So right now this plugin works by inserting real code into your text editor. This is basically inherited from the implementation in
modeling-app
. The pro of this is that the 'ghost text' gets proper syntax coloring and behaves like real code. The con is that when we insert ghost text, it generates real change events, so the actual code in the editor changes when you have ghost text displayed. So you can get into situations like:This is obviously less than ideal, and ends up with (in our case) having a method exposed like
shouldTakeUpdate
which lets upstream systems ignore change events. But the whole necessity of thatshouldTakeUpdate
method is driven just by the fact that ghost text is, surprisingly, real code in your editor.The text was updated successfully, but these errors were encountered: