ember-sortable 4.0.3 → 5.0.1

package/CODE_OF_CONDUCT.md

@@ -1,6 +0,0 @@
-# Code Of Conduct
-
-The `ember-sortable` core team and and the broader `Ember` community are committed to everyone having a safe and inclusive experience.
-
-- Our **Community Guidelines / Code of Conduct** can be found at [emberjs.com/guidelines](https://emberjs.com/guidelines/)
-- A history of updates to this page is located at [https://github.com/emberjs/website/commits/master/source/guidelines.html.erb](https://github.com/emberjs/website/commits/master/source/guidelines.html.erb)

package/MIGRATION_GUIDE_MODIFIERS.md

@@ -1,95 +0,0 @@
-# Ember-sortable
-
-## Migration Guide (Components -> Modifiers)
-
-To use modifiers, you must use angle-bracket syntax
-
-### New Root component
-
-1. Instead of using `sortable-group` as a component, use `sortable-group` as a modifier
-   any element. You no longer need to tell `sortable-group` about the models, so the `each`
-   uses the models directly.
-
-**Old Component**
-
-```hbs
-{{#sortable-group model=model.items onChange=(action "reorderItems") as |group|}}
-  {{#each group.model as |item|}}
-```
-
-**New Component**
-
-```hbs
-<ol {{sortable-group onChange=(action "reorderItems")}}>
-  {{#each model.items as |item|}}
-```
-
-2. Each `item` can be represented by any dom element or component using angle-bracket syntax
-
-**Old Component**
-
-```hbs
-{{#sortable-group model=model.items onChange=(action 'reorderItems') as |group|}}
-  {{#each group.model as |item|}}
-    {{#group.item model=item}}
-      {{item.name}}
-    {{/group.item}}
-  {{/each}}
-{{/sortable-group}}
-```
-
-**New Component with modifier**
-
-```hbs
-<ol {{sortable-group onChange=(action 'reorderItems')}}>
-  {{#each model.items as |item|}}
-    <li {{sortable-item model=item}}>
-      {{item.name}}
-    </li>
-  {{/each}}
-</ol>
-```
-
-3. The Handle is also any element with a `sortable-handle` applied to it.
-
-**Old Component**
-
-```hbs
-{{#sortable-group model=model.items onChange=(action "reorderItems") as |group|}}
-  {{#each group.model as |modelItem|}}
-    {{#group.item model=modelItem as|item|}}
-      {{modelItem.name}}
-      {{#item.handle}}
-        <span class="handle">&varr;</span>
-      {{/item.handle}}
-    {{/group.item}}
-  {{/each}}
-{{/sortable-group}}
-```
-
-**New Component with modifier**
-
-```hbs
-<ol {{sortable-group onChange=(action 'reorderItems')}}>
-  {{#each model.items as |item|}}
-    <li {{sortable-item model=item}}>
-      {{item.name}}
-      <span class='handle' {{sortable-handle}}>&varr;</span>
-    </li>
-  {{/each}}
-</ol>
-```
-
-4. The modifier `groupModel` property is no longer supported. The equivalent can
-   be accomplished by the `action` helper or the new `fn` helper.
-
-```hbs
-<ol {{sortable-group onChange=(action 'reorderItems' model)}}>
-  {{#each model.items as |item|}}
-    <li {{sortable-item model=item}}>
-      {{item.name}}
-      <span class='handle' {{sortable-handle}}>&varr;</span>
-    </li>
-  {{/each}}
-</ol>
-```

package/MIGRATION_GUIDE_V2.md

@@ -1,120 +0,0 @@
-# Ember-sortable
-
-## Migration Guide (v1 -> v2)
-
-[High Order Components](#Higher Order Components) or [Modifiers](/MIGRATION_GUIDE_MODIFIERS.md)
-
-### Higher Order Components
-
-`Ember-sortable` can now be built using [higher order components](https://v4.chriskrycho.com/2018/higher-order-components-in-emberjs.html)
-
-1. The array of models are now yielded out by `sortable-group`
-
-**V1**
-
-```hbs
-{{#sortable-group onChange=(action "reorderItems") as |group|}}
-  {{#each model.items as |item|}}
-```
-
-**V2**
-
-```hbs
-{{#sortable-group model=model.items onChange=(action "reorderItems") as |group|}}
-  {{#each group.model as |item|}}
-```
-
-2. Each `item` can be represented by the yielded `sortable-item` instead of directly using `sortable-item` and passing the `group` manually.
-
-**V1**
-
-```hbs
-{{#sortable-group onChange=(action 'reorderItems') as |group|}}
-  {{#each model.items as |item|}}
-    {{#sortable-item model=item group=group handle='.handle'}}
-      {{item.name}}
-      <span class='handle'>&varr;</span>
-    {{/sortable-item}}
-  {{/each}}
-{{/sortable-group}}
-```
-
-**V2**
-
-```hbs
-{{#sortable-group model=model.items onChange=(action 'reorderItems') as |group|}}
-  {{#each group.model as |item|}}
-    {{#group.item model=item}}
-      ...
-    {{/group.item}}
-  {{/each}}
-{{/sortable-group}}
-```
-
-3. It is recommended to use the yielded `sortable-handle` instead of referencing `handle` by `class`, as it guarantees accessibility support.
-
-**V1**
-
-```hbs
-{{#sortable-group onChange=(action 'reorderItems') as |group|}}
-  {{#each model.items as |item|}}
-    {{#sortable-item model=item group=group handle='.handle'}}
-      {{item.name}}
-      <span class='handle'>&varr;</span>
-    {{/sortable-item}}
-  {{/each}}
-{{/sortable-group}}
-```
-
-**V2**
-
-```hbs
-{{#sortable-group model=model.items onChange=(action "reorderItems") as |group|}}
-  {{#each group.model as |modelItem|}}
-    {{#group.item model=item as|item|}}
-      {{modelItem.name}}
-      {{#item.handle}}
-        <span class="handle">&varr;</span>
-      {{/item.handle}}
-    {{/group.item}}
-  {{/each}}
-{{/sortable-group}}
-```
-
-4. `groupModel` is still supported via `groupModel` instead of `model`
-
-**V1**
-
-```hbs
-{{#sortable-group model=model onChange=(action "reorderItems") as |group|}}
-  {{#each model.items as |item|}}
-  ...
-{{/sortable-group}}
-```
-
-**V2**
-
-```hbs
-{{#sortable-group groupModel=model model=model.items onChange=(action "reorderItems") as |group|}}
-  {{#each group.model as |item|}}
-  ...
-{{/sortable-group}}
-```
-
-### Modifiers
-
-### Accessibility support
-
-1. Keyboard navigation is built into `ember-sortable`.
-2. `a11yItemName`, `a11yAnnouncementConfig`, `itemVisualClass`, `handleVisualClass` can be supplied to enhance the accessibility experience.
-3. Refer to [Accessibility Section](/README.md#Accessibility) for more details.
-
-```hbs
-  {{#sortable-group a11yAnnouncementConfig=a11yAnnouncementConfig a11yItemName="spanish number" itemVisualClass=itemVisualClass handleVisualClass=handleVisualClass onChange=(action "update") model=model.items as |group|}}
-```
-
-### Testing
-
-1. The `drag` and `reorder` test helpers are no longer global `async` helpers. They are now importable.
-
-Refer to [Testing Section](/README.md#Testing) for more details.

package/Makefile

@@ -1,24 +0,0 @@
-demo:
-	@echo ""
-	@echo "===> Checking out gh-pages"
-	@echo ""
-	git checkout gh-pages
-	git reset --hard master
-	@echo ""
-	@echo "===> Building demo"
-	@echo ""
-	ember build -e production -o demo
-	@echo ""
-	@echo "===> Committing demo"
-	@echo ""
-	git add demo
-	git commit -m "Build demo" --no-verify
-	@echo ""
-	@echo "===> Pushing gh-pages"
-	@echo ""
-	git push origin gh-pages -f --no-verify
-	@echo ""
-	@echo "===> Cleaning up"
-	@echo ""
-	git checkout master
-	rm -rf demo

package/RELEASE.md

@@ -1,60 +0,0 @@
-# Release Process
-
-Releases are mostly automated using
-[release-it](https://github.com/release-it/release-it/) and
-[lerna-changelog](https://github.com/lerna/lerna-changelog/).
-
-## Preparation
-
-Since the majority of the actual release process is automated, the primary
-remaining task prior to releasing is confirming that all pull requests that
-have been merged since the last release have been labeled with the appropriate
-`lerna-changelog` labels and the titles have been updated to ensure they
-represent something that would make sense to our users. Some great information
-on why this is important can be found at
-[keepachangelog.com](https://keepachangelog.com/en/1.0.0/), but the overall
-guiding principle here is that changelogs are for humans, not machines.
-
-When reviewing merged PR's the labels to be used are:
-
-* breaking - Used when the PR is considered a breaking change.
-* enhancement - Used when the PR adds a new feature or enhancement.
-* bug - Used when the PR fixes a bug included in a previous release.
-* documentation - Used when the PR adds or updates documentation.
-* internal - Used for internal changes that still require a mention in the
-  changelog/release notes.
-
-## Release
-
-Once the prep work is completed, the actual release is straight forward:
-
-* First, ensure that you have installed your projects dependencies:
-
-```sh
-yarn install
-```
-
-* Second, ensure that you have obtained a
-  [GitHub personal access token][generate-token] with the `repo` scope (no
-  other permissions are needed). Make sure the token is available as the
-  `GITHUB_AUTH` environment variable.
-
-  For instance:
-
-  ```bash
-  export GITHUB_AUTH=abc123def456
-  ```
-
-[generate-token]: https://github.com/settings/tokens/new?scopes=repo&description=GITHUB_AUTH+env+variable
-
-* And last (but not least 😁) do your release.
-
-```sh
-npx release-it
-```
-
-[release-it](https://github.com/release-it/release-it/) manages the actual
-release process. It will prompt you to to choose the version number after which
-you will have the chance to hand tweak the changelog to be used (for the
-`CHANGELOG.md` and GitHub release), then `release-it` continues on to tagging,
-pushing the tag and commits, etc.