(MAINT) Full linter fix

Author: Lukeaber

.jshintrc

@@ -1,9 +1,5 @@
 {
-  "predef": [
-    "document",
-    "window",
-    "-Promise"
-  ],
+  "predef": ["document", "window", "-Promise"],
   "browser": true,
   "boss": true,
   "curly": true,

AUTHORS.md

@@ -1 +1 @@
-["Dray Lacy", "Nathaniel Bibler", "Yoran Brondsema", "Jonathan Newman", "Steven Foote", "Manuel Wiedenmann", "Katlin Anderson"]
+["Dray Lacy", "Nathaniel Bibler", "Yoran Brondsema", "Jonathan Newman", "Steven Foote", "Manuel Wiedenmann", "Katlin Anderson"]

CHANGELOG.md

@@ -6,141 +6,141 @@ All notable changes to this project will be documented in this file. See [standa
 
 ### Security
 
-* Bump jquery from 3.3.1 to 3.4.0 ([05c21dd](https://github.com/IvyApp/ivy-tabs/commit/05c21dd))
+- Bump jquery from 3.3.1 to 3.4.0 ([05c21dd](https://github.com/IvyApp/ivy-tabs/commit/05c21dd))
 
 ## [3.3.0][] / 2018-03-17
 
-* Add "aria-live" to tablists for reporting tab changes to the user.
-* Add optional "aria-label" to tablists to improve screenreader reporting.
-* Give active tabpanels tabindex 0 to allow keyboard navigation to the active panel content.
-* Use a temporary "presentation" role for tablists until tabs are inserted and the "tablist" role is then allowed. See emberjs/ember.js#16379.
+- Add "aria-live" to tablists for reporting tab changes to the user.
+- Add optional "aria-label" to tablists to improve screenreader reporting.
+- Give active tabpanels tabindex 0 to allow keyboard navigation to the active panel content.
+- Use a temporary "presentation" role for tablists until tabs are inserted and the "tablist" role is then allowed. See emberjs/ember.js#16379.
 
 ## [3.2.0][] / 2018-03-07
 
-* No longer trigger selection actions during Component destruction.
-* [#33](https://github.com/IvyApp/ivy-tabs/pull/33) Remove jQuery usage. Thanks to @smfoote and @dxprog.
-* [#37](https://github.com/IvyApp/ivy-tabs/pull/37) Move to modules API. Thanks to @sutori.
+- No longer trigger selection actions during Component destruction.
+- [#33](https://github.com/IvyApp/ivy-tabs/pull/33) Remove jQuery usage. Thanks to @smfoote and @dxprog.
+- [#37](https://github.com/IvyApp/ivy-tabs/pull/37) Move to modules API. Thanks to @sutori.
 
 ## [3.1.0][] / 2016-12-02
 
-* [#32](https://github.com/IvyApp/ivy-tabs/pull/32) Add Ember 2.10 support.
+- [#32](https://github.com/IvyApp/ivy-tabs/pull/32) Add Ember 2.10 support.
 
 ## [3.0.2][] / 2016-10-14
 
-* Remove `throw` when a tab is not found by index or model. Add "dynamic tabs" example page to the dummy app.
-* Switch from globals to modules.
+- Remove `throw` when a tab is not found by index or model. Add "dynamic tabs" example page to the dummy app.
+- Switch from globals to modules.
 
 ## [3.0.1][] / 2016-10-12
 
-* [#25](https://github.com/IvyApp/ivy-tabs/issues/25) Fix a deprecation warning when tab panels are defined before the tab list.
+- [#25](https://github.com/IvyApp/ivy-tabs/issues/25) Fix a deprecation warning when tab panels are defined before the tab list.
 
 ## [3.0.0][] / 2016-08-31
 
 **This release introduces several breaking changes from the 2.x series.** Refer
 to the README for current usage.
 
-* [#24](https://github.com/IvyApp/ivy-tabs/pull/24) "Namespace" components under `ivy-tabs-*`
-* [#23](https://github.com/IvyApp/ivy-tabs/pull/23) Remove `tagName` values except for tabs, which are now anchor tags by default.
-* [#21](https://github.com/IvyApp/ivy-tabs/pull/21) Select tabs by a (now required) model value, rather than tab index.
-    * Rename `selectedIndex` on `ivy-tabs` to `selection`.
-    * Move `on-select` action from `ivy-tabs` to individual tabs.
-* [#22](https://github.com/IvyApp/ivy-tabs/pull/22) Remove isVisible manipulation and rely on application styles for presentation management.
+- [#24](https://github.com/IvyApp/ivy-tabs/pull/24) "Namespace" components under `ivy-tabs-*`
+- [#23](https://github.com/IvyApp/ivy-tabs/pull/23) Remove `tagName` values except for tabs, which are now anchor tags by default.
+- [#21](https://github.com/IvyApp/ivy-tabs/pull/21) Select tabs by a (now required) model value, rather than tab index.
+  - Rename `selectedIndex` on `ivy-tabs` to `selection`.
+  - Move `on-select` action from `ivy-tabs` to individual tabs.
+- [#22](https://github.com/IvyApp/ivy-tabs/pull/22) Remove isVisible manipulation and rely on application styles for presentation management.
 
 ## [2.0.0][] / 2016-04-17
 
 **This release drops support for Ember < 2.3.**
 
-* [#13](https://github.com/IvyApp/ivy-tabs/pull/13) Data down, Actions up.
-* [#15](https://github.com/IvyApp/ivy-tabs/pull/15) Add aria-hidden to ivy-tab-panel.
-* [#12](https://github.com/IvyApp/ivy-tabs/pull/12) Convert to contextual components.
-* Upgrade to Ember CLI 2.5.0.
+- [#13](https://github.com/IvyApp/ivy-tabs/pull/13) Data down, Actions up.
+- [#15](https://github.com/IvyApp/ivy-tabs/pull/15) Add aria-hidden to ivy-tab-panel.
+- [#12](https://github.com/IvyApp/ivy-tabs/pull/12) Convert to contextual components.
+- Upgrade to Ember CLI 2.5.0.
 
 ## [1.2.0][] / 2016-03-24
 
-* Upgrade `ember-cli` to 2.4.2.
-* Use block params instead of `parentView`.
-* Remove index file.
-* Remove standalone builds.
-* Select the next tab when the active, first tab is removed.
-* Retain tab selection if a preceding tab is removed.
+- Upgrade `ember-cli` to 2.4.2.
+- Use block params instead of `parentView`.
+- Remove index file.
+- Remove standalone builds.
+- Select the next tab when the active, first tab is removed.
+- Retain tab selection if a preceding tab is removed.
 
 ## [1.1.0][] / 2015-05-21
 
-* Upgrade addon to ember-cli 0.2.4.
-* Fix an issue with initial value of `selected-index` not being applied.
-* Add touch support.
-* Upgrade to ember-cli 0.2.0.
-* Upgrade to ember 1.10.0.
+- Upgrade addon to ember-cli 0.2.4.
+- Fix an issue with initial value of `selected-index` not being applied.
+- Add touch support.
+- Upgrade to ember-cli 0.2.0.
+- Upgrade to ember 1.10.0.
 
 ## [1.0.0][] / 2015-02-19
 
-* Ensure selected-index remains 0 if all tabs are removed.
-* Upgrade to ember-cli 0.1.5.
-* Upgrade to ember 1.9.1 in dummy app.
-* Remove unnecessary ember-data dependency in dummy app.
-* Remove version suffix from ivy-tabs.js.
-* More tooling changes. Should now be usable as a Bower package, outside of an
+- Ensure selected-index remains 0 if all tabs are removed.
+- Upgrade to ember-cli 0.1.5.
+- Upgrade to ember 1.9.1 in dummy app.
+- Remove unnecessary ember-data dependency in dummy app.
+- Remove version suffix from ivy-tabs.js.
+- More tooling changes. Should now be usable as a Bower package, outside of an
   Ember CLI app.
-* Remove deprecated selectedIndex property.
-* Convert to an ember-cli addon.
-* Rename toplevel global from `ivy.tabs` to `IvyTabs`.
+- Remove deprecated selectedIndex property.
+- Convert to an ember-cli addon.
+- Rename toplevel global from `ivy.tabs` to `IvyTabs`.
 
 ## [0.3.0][] / 2014-11-05
 
-* Move away from `broccoli-dist-es6-module`. Instead, use
+- Move away from `broccoli-dist-es6-module`. Instead, use
   `broccoli-es6-module-transpiler`, which supports the latest version of the
   ES6 module transpiler. Rather than generating separate distributions for
   `amd`, `cjs`, `named-amd` and `globals`, we now output a single "bundle"
   format.
-* Deprecate `selectedIndex`, use `selected-index` instead.
+- Deprecate `selectedIndex`, use `selected-index` instead.
 
 ## [0.2.0][] / 2014-11-03
 
-* Add keyboard navigation.
+- Add keyboard navigation.
 
 ## [0.1.6][] / 2014-11-04
 
-* Build tooling changes.
+- Build tooling changes.
 
 ## [0.1.5][] / 2014-11-03
 
-* Fix issue with tab index being out of order. This was being caused by
+- Fix issue with tab index being out of order. This was being caused by
   a reliance on `didInsertElement` firing in a particular order, which Ember
   doesn't guarantee. Instead, the actions are now fired inside the `init` and
   `willDestroy` methods of the component classes.
 
 ## [0.1.4][] / 2014-11-01
 
-* Fix incorrect spelling of "aria-labelledby".
+- Fix incorrect spelling of "aria-labelledby".
 
 ## [0.1.3][] / 2014-11-01
 
-* Rewrite internals to make selectedIndex canonical. Previously, the "active
+- Rewrite internals to make selectedIndex canonical. Previously, the "active
   tab" object was canonical, and the selectedIndex was calculated based on this
   tab's index in the tabs array. That has been flipped on its head so now, the
   "selected tab" is calculated based on the selectedIndex.
-* Replace use of `Ember.computed.readOnly`. This method didn't exist prior to
+- Replace use of `Ember.computed.readOnly`. This method didn't exist prior to
   Ember 1.5.
-* Change "aria-expanded" to a read-only alias.
+- Change "aria-expanded" to a read-only alias.
 
 ## [0.1.2][] / 2014-10-30
 
-* When active tab is removed, select the previous tab (if any).
+- When active tab is removed, select the previous tab (if any).
 
 ## [0.1.1][] / 2014-10-23
 
-* Ensure `ivy-tab-panel`'s `isVisible` property is a Boolean. Previously it was
+- Ensure `ivy-tab-panel`'s `isVisible` property is a Boolean. Previously it was
   an alias to `active`, which returns a String so that it can be used as
   a classname binding. The problem is, Ember observes `isVisible` and calls
   jQuery's `toggle` function while passing in the value of `isVisible` to
-  determine whether to show or hide the element.  In this case, `isVisible` was
+  determine whether to show or hide the element. In this case, `isVisible` was
   returning a String, which jQuery would interpret as an easing function. This
   would result in the tab panels animating in and out when switching between
   tabs.
 
 ## [0.1.0][] / 2014-10-23
 
-* Initial release.
+- Initial release.
 
 [0.1.0]: https://github.com/IvyApp/ivy-tabs/tree/v0.1.0
 [0.1.1]: https://github.com/IvyApp/ivy-tabs/compare/v0.1.0...v0.1.1

CODE_OF_CONDUCT.md

@@ -4,26 +4,26 @@ We want to keep the Puppet communities awesome, and we need your help to keep it
 that way. While we have specific guidelines for various tools (see links below),
 in general, you should:
 
-* **Be nice**: Be courteous, respectful and polite to fellow community members. No
+- **Be nice**: Be courteous, respectful and polite to fellow community members. No
   offensive comments related to gender, gender identity or expression, sexual
   orientation, disability, physical appearance, body size, race, religion; no
   sexual images in public spaces, real or implied violence, intimidation,
   oppression, stalking, following, harassing photography or recording, sustained
   disruption of talks or other events, inappropriate physical contact, doxxing, or
   unwelcome sexual attention will be tolerated. We like nice people way better
   than mean ones!
-* **Encourage diversity and participation**: Make everyone in our community feel
+- **Encourage diversity and participation**: Make everyone in our community feel
   welcome, regardless of their background, and do everything possible to encourage
   participation in our community.
-* **Focus on constructive criticisms**: When offering suggestions, whether in online
+- **Focus on constructive criticisms**: When offering suggestions, whether in online
   discussions or as comments on a pull request, you should always use welcoming
   and inclusive language. Be respectful of differing viewpoints and the fact that
   others may not have the same experiences you do. Offer suggestions for
   improvement, rather than focusing on mistakes. When others critique your work or
   ideas, gracefully accept the criticisms and default to assuming good intentions.
-* **Keep it legal**: Basically, don't get us in trouble. Share only content that you
+- **Keep it legal**: Basically, don't get us in trouble. Share only content that you
   own, do not share private or sensitive information, and don't break the law.
-* **Stay on topic**: Keep conversation in a thread on topic, whether that's a pull
+- **Stay on topic**: Keep conversation in a thread on topic, whether that's a pull
   request or a Slack conversation or anything else. Make sure that you are posting
   to the correct channel and remember that nobody likes spam.
 
@@ -34,19 +34,19 @@ do need a fair way to deal with people who do harm to our community. Extreme
 violations of a threatening, abusive, destructive, or illegal nature will be
 addressed immediately and are not subject to 3 strikes.
 
-* First occurrence: We'll give you a friendly, but public, reminder that the
+- First occurrence: We'll give you a friendly, but public, reminder that the
   behavior is inappropriate according to our guidelines.
-* Second occurrence: We'll send you a private message with a warning that any
+- Second occurrence: We'll send you a private message with a warning that any
   additional violations will result in removal from the community.
-* Third occurrence: Depending on the violation, we might need to delete or ban
+- Third occurrence: Depending on the violation, we might need to delete or ban
   your account.
 
 Notes:
 
-* Obvious spammers are banned on first occurrence. If we don’t do this, we’ll
+- Obvious spammers are banned on first occurrence. If we don’t do this, we’ll
   have spam all over the place.
-* Violations are forgiven after 6 months of good behavior, and we won’t hold a grudge.
-* People who are committing minor formatting / style infractions will get some
+- Violations are forgiven after 6 months of good behavior, and we won’t hold a grudge.
+- People who are committing minor formatting / style infractions will get some
   education, rather than hammering them in the 3 strikes process.
 
 Contact [email protected] to report abuse or appeal violations. This email list
@@ -67,4 +67,4 @@ Credit to [01.org](https://01.org/community/participation-guidelines) and
 starting point for many of these guidelines.
 
 The Event Code of Conduct is based on the [example policy from the Geek Feminism wiki](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment),
-created by the Ada Initiative and other volunteers. The [PyCon Code of Conduct](https://github.com/python/pycon-code-of-conduct) also served as inspiration.
+created by the Ada Initiative and other volunteers. The [PyCon Code of Conduct](https://github.com/python/pycon-code-of-conduct) also served as inspiration.