RichContent autocomplete not required #3757
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jotoeri
requested review from
PVince81,
vinicius73,
susnux,
skjnldsv,
marcoambrosini and
danxuliu
susnux
reviewed
Feb 15, 2023
Signed-off-by: Jonas Rittershofer <jotoeri@users.noreply.github.com>
jotoeri
force-pushed
the
fix/autocomplete
branch
from
4c5de7e
to
1ebaea3
Compare
susnux
approved these changes
Feb 16, 2023
raimund-schluessler
added
enhancement
raimund-schluessler
approved these changes
Feb 16, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since we don't need autocompletion on forms, we would just pass an empty function (as talk does btw., too 😉). So why not doing this here.