Skip to content

Conversation

@jvorcak
Copy link
Member

@jvorcak jvorcak commented Dec 4, 2017

No description provided.

@jvorcak jvorcak requested a review from jukben December 4, 2017 13:15
Copy link
Collaborator

@jukben jukben left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to go more for non-breaking change. It would be awesome to introduce another type of caretPosition: "next" – which should have this very behavior.

@jvorcak jvorcak force-pushed the fix/space-after-emoji branch 2 times, most recently from e8cfee9 to 383603e Compare January 26, 2018 23:26
@jvorcak
Copy link
Member Author

jvorcak commented Jan 26, 2018

@jukben I've added next caretPosition: 'next' and adjusted Cypress tests. Hopefully it's better now. But I still think that this should be a default behavior in a next major release.

@jukben jukben force-pushed the fix/space-after-emoji branch from 383603e to 21db57c Compare January 28, 2018 20:03
@jukben
Copy link
Collaborator

jukben commented Jan 28, 2018

Wonderful contribution! Thanks a lot. I particularly like how you have refactored the E2E test. Good job, indeed.

I appreciate your opinion and I will bear it in mind and I will change the default value of this option in favor "next" in the next major release. 👍

@jukben jukben merged commit 6190935 into master Jan 28, 2018
@jvorcak jvorcak deleted the fix/space-after-emoji branch January 28, 2018 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants