Member position #456
Merged
Member position #456
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
🦋 Changeset detectedLatest commit: 8154a06 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
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 |
edolix
reviewed
Mar 8, 2022
edolix
reviewed
Mar 10, 2022
|
Looks good! Do you want to include the changes for "js" in this PR? |
edolix
reviewed
Mar 16, 2022
edolix
reviewed
Mar 16, 2022
Comment on lines
5
to
7
| if (!options.payload) { | ||
| return | ||
| } |
There was a problem hiding this comment.
If this is an error for us, i would either log something or throw an error ?
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.
Checklist
requestedPositionandcurrentPositionto the member interfacemember.updatedlayout.changedevents in case the end-user asked formember.updated. Not the reverse since we don't needmember.updateddata to trigger alayout.changed.currentPositionto a (normal) server-sidemember.updatedeventlayout.changedevents and generate localmember.updatedbased on the data of the previous and currentlayout.changed.