Packages updates

This release has some audit fixes. I will look more into this to upgrade it to vue3

Documentation update

Updated the documentation on how to use the library for NuxtJS and SSR.

CSS Changes and dependency vulnerability fix

• Fixed the button CSS for cancel button
• Dependency vulnerability fix

Event Emitters

Added

• Added couple of new event emitters dropInOriginalBucket and dropInDestinationBucket.
• Added more documentation for events in the README.

Minor Update on CSS

Changed

• Changed the css class name to be more specific to the component
• Changed the css value to make the cards not tilt
• Changed the original container to scroll vertically rather than horizontally.
• Bug fix: When everything from original bucket was moved to dropzones, original used to collapse. Now, it doesnt and the user can move the cards back to original.

Big update enabling user's to add objects

Added

• Added new props
  • inPlace: makes in place changes to props dropzones. Enabled by default
  • enableSave: Enable Save button
  • enableCancel: Enable Cancel button
• Changelog.md file added

Changed

• Introduced vue slots for the content of each card. Users can have their own card components
• Enabling list of objects to be passed rather than string. Also, works for string. The change will not break previous version.
• save event's response body has changed to reflect the items in original list and dropzones when save pressed.
• Modified documentation

Removed

• Removed the logic for validation. Parent components can handle this during save

Documentation and Test addition

• Added more documentation

  • Code of Conduct
  • Template for creating pull request
  • Templates for raising an issue
  • Update on Readme.md to include more details on installation and usage

• Added Test Framework

  • Added Jest test for the component
  • Tests generate code coverage report
  • Added test cases. Current coverage about ~52%.

• Husky implementation

  • Added husky so that the test is ran every time devs try to push to improve code quality

Testing release

v0.0.12

0.0.12 update

First Final release

Automation of npm publish on a master branch when the version changes.

To create a release, create a Pull Request to the master branch with the following requirement:

• Merge header must only include release version like: 'Release x.y.z' where x,y,z are the semantic versioning
• Create a separate Pull Request just for publishing the release to NPM.