-
Notifications
You must be signed in to change notification settings - Fork 645
Fix MarkdownEditor suggestions filtering bug and allow lazy-loading suggestions
#2424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: d832344 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
size-limit report 📦
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥳
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The lazy loading of emojis, references and suggestions is killer.
The bug fixes here are stuff we've logged in the pull requests app we are building too. This should resolve our same issues.
Thanks for leading the charge here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Scoped to drafts, ship it
MarkdownEditorsuggestions break when querying by 3 or more characters #2423MarkdownEditorasks for the data. Then they can cache the data for future rendering. The new prop types look likeemojiSuggestions?: Emoji[] | (() => Promise<Emoji[]>). This resolvesMarkdownEditorshould allow lazy-loading suggestions #2422MarkdownEditortest suite to perform the mocking ofoffsetHeighton theHTMLElementprototype in abeforeAllinstead of on the element instances themselves in alayoutEffect. This is far less buggy and removes any chance of race conditions (which I was encountering when moving to async event handlers for rendering suggestions).