docs: fix default dropzone class names in Droppable and SortAnimation module example - #680
Open
Reyo77 wants to merge 1 commit into
Open
docs: fix default dropzone class names in Droppable and SortAnimation module example#680Reyo77 wants to merge 1 commit into
Reyo77 wants to merge 1 commit into
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR implements or fixes...
src/Droppable/README.md: Corrects the default CSS class names in the documentation table fromdraggable-droppable--active/draggable-droppable--occupiedto the actual defaults used in the implementation (draggable-dropzone--activeanddraggable-dropzone--occupied).src/Plugins/SortAnimation/README.md: Fixes the ESM<script type="module">example which incorrectly imported and instantiatedSnappableinstead ofSortAnimation.This PR closes the following issues...
N/A
Does this PR require the Docs to be updated?
Yes, this PR directly updates and corrects the documentation.
Does this PR require new tests?
No (documentation fix only; existing test suites pass).
This branch been tested on... (click all that apply / add new items)
npm test)Browsers: