EmojiInput refactoring #2093

Closed
hj wants to merge 0 commits from gitlab-mr-iid-824 into develop
Member

Closes #565

  • Reimplemented emoji-input as a component that enhances existing element via slots.
  • Replaced copy-paste suggetsions in post status form
  • Standardized format for autocomplete suggestions
  • Switched to PopperJS popper-vue sucks
  • Made suggestor async by default? for the next time
  • Fixed bugs
  • Rename emoji-input?
Closes #565 * [x] Reimplemented emoji-input as a component that enhances existing element via slots. * [x] Replaced copy-paste suggetsions in post status form * [x] Standardized format for autocomplete suggestions * ~~Switched to PopperJS~~ popper-vue sucks * ~~Made suggestor async by default?~~ for the next time * [x] Fixed bugs * [ ] Rename emoji-input?
Author
Member

remove leftovers

remove leftovers
Author
Member

remove value it's unused anymore

remove `value` it's unused anymore
Author
Member

needs better documentation

needs better documentation
Author
Member

found a bug - mention replacement doens't put a space at the end

found a bug - mention replacement doens't put a space at the end
Author
Member

another bug - clicking doesn't work for some reason again.... ugh

another bug - clicking doesn't work for some reason again.... ugh
Author
Member

mentioned bugs fixed + added more documentation

mentioned bugs fixed + added more documentation
Member

resize doesn't take arguments

resize doesn't take arguments
Member

does passing an event here work correctly?

does passing an event here work correctly?
Member

ternary might be clearer here I think aScore += a.imageUrl ? 10 : 0

ternary might be clearer here I think `aScore += a.imageUrl ? 10 : 0`
Author
Member

it does. neither of those do anything to event, just another opportunity to sync state.

it does. neither of those do anything to event, just another opportunity to sync state.
Member

for curried functions like this use arrow syntax, const suggestEmoji = emojis => input => { ... }

for curried functions like this use arrow syntax, `const suggestEmoji = emojis => input => { ... }`
Member

Suggest exporting everything to enable unit tests for every function, even if it's not actually done here

Suggest exporting everything to enable unit tests for every function, even if it's not actually done here
Member

(bScore - aScore) * 10

(bScore - aScore) * 10
Member

Would prefer the old one here, nice to be able to tell apart our custom components from others

Would prefer the old one here, nice to be able to tell apart our custom components from others
Member

it's just an event coming from a different source which is always a bit spooky, but if it works it works

it's just an event coming from a different source which is always a bit spooky, but if it works it works
Author
Member

fixed

fixed
Author
Member

fixed and also in other places like

--score += boolean
++score += boolean ? 1 : 0

for clarity

fixed and also in other places like ```diff --score += boolean ++score += boolean ? 1 : 0 ``` for clarity
Member

small whoops: <emoji-input> </EmojiInput>

small whoops: `<emoji-input> </EmojiInput>`
Member

is it some style thing to () a single argument? I've left the parens out if not needed. I don't mind too much either way but now we have 2 different styles on the same line w

is it some style thing to () a single argument? I've left the parens out if not needed. I don't mind too much either way but now we have 2 different styles on the same line w
Member

yeah LGTM all in all

yeah LGTM all in all

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pleroma/pleroma-fe!2093
No description provided.