Giter Club home page Giter Club logo

ember-modal-service's Introduction

ember-modal-service

Build Status GitHub version NPM version Dependency Status codecov Greenkeeper badge Ember Observer Score

An ember-cli addon to manage modals as promises.

Information

NPM

Install in ember-cli application

In your application's directory:

ember install ember-modal-service

Usage

Register the modal container

All the modals are shown inside the modal container once opened.

{{! templates/application.hbs }}
<ModalContainer />

Create a modal component

In order to register a new modal, you need to register the modal object in the application container using the preffix modal-*.

// app/components/modal-foo.js
import ModalComponent from 'ember-modal-service/components/modal';

export default class FooModal extends ModalComponent {
   data = this.model.options.data; 
}
{{! app/templates/modal-foo.hbs }}

<div>
  <p>{{data}}</p>
</div>

Opening the modal

import Controller from '@ember/controller';
import { action } from '@ember/object';

export default class Controller extends Controller {
  // Inject the service
  @service modal;

  @action
  async doSomething() {
    // To open a modal use the method `open` with the modal name and the options for the modal.
    try {
      const result = await this.modal.open('foo', { bar: 'bar' });

      // Modal have been resolved
    } catch(e) {
      // Modal have been rejected
    }
  }

Other useful things

You can close all modals by using the close method.

this.modal.close();

Or just some of them.

this.modal.close((modal) => {
  return modal.name === 'foo';
});

this.modal.close('name', 'foo');

Base modal component provides resolve & reject actions so you can implement basic closing behaviour directly on the template. You can pass any arguments you want the modal to be resolved / rejected with

<button {{fn this.reject "foo" "bar"}}>Resolve modal with two args</button>

<button {{fn this.reject "foo" "bar"}}>Reject modal with two args</button>

Contribute

If you want to contribute to this addon, please read the CONTRIBUTING.md.

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

Authors

See the list of contributors who participated in this project.

License

This project is licensed under the MIT License - see the LICENSE.md file for details

ember-modal-service's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ember-modal-service's Issues

Glimmer components support

As Octane edition is around the corner it seem good time to get support (or at least define/discuss the plan if it's not defined yet) for Glimmer Components.

ember-cli-babel 5.x has been deprecated

When using ember-modal-service with Ember 3.3.0, I get the following deprecation message:

DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at least ember-cli-babel 6.6. Version 5.1.10 located: ...

Default promise actions?

Hi,

I'm curious if there's anyway to set a default set of actions to be called for a single modal or for all modals.

For example, I'd like to add the overflow: hidden style to the <body> element when I open any modal and then remove the inline styling when I close the modal.

It seems that the obvious way to handle this is something like:

      this.get('modal').open('my-modal, { formModel: this.model }).then(
        document.getElementsByTagName("BODY")[0].setAttribute("style", "overflow: hidden"),
        function() {
          document.getElementsByTagName("BODY")[0].setAttribute("style", "overflow: visible");
        }
      );

But this means I now need to remember to add this to all calls to modal.open, which seems too fragile...

An in-range update of ember-cli-inject-live-reload is breaking the build 🚨

The devDependency ember-cli-inject-live-reload was updated from 2.0.1 to 2.0.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-inject-live-reload is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 42 commits.

  • f3e9bea Release 2.0.2
  • 4c4ebc0 Respect liveReloadPort even if same as ember server port (#113)
  • 9581f3b Respect liveReloadPort even if same as ember server port
  • ba3de60 Change entry-point script. (#123)
  • 8b732e0 Change entry-point script.
  • 00616ce Re-roll yarn.lock due to issues with [email protected] (#122)
  • f608771 Re-roll yarn.lock due to issues with [email protected]
  • 5a37c1d [Security] Bump eslint-utils from 1.3.1 to 1.4.2
  • d7fd57f [Security] Bump lodash from 4.17.11 to 4.17.14
  • e9738c0 Bump express from 4.17.0 to 4.17.1
  • f1a66fc Bump express from 4.16.4 to 4.17.0
  • 0367c3f Bump eslint from 5.15.3 to 5.16.0
  • 6800f6d Bump ember-cli-version-checker from 3.1.2 to 3.1.3
  • 3ee4ac7 Bump eslint from 5.15.2 to 5.15.3
  • 3e43143 Bump eslint from 5.15.1 to 5.15.2

There are 42 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.12.3 to 15.12.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v15.12.4

15.12.4 (2018-11-30)

Bug Fixes

  • remove unnecessary branch parameter from push function (ffe1062)
Commits

The new version differs by 1 commits.

  • ffe1062 fix: remove unnecessary branch parameter from push function

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @semantic-release/git is breaking the build 🚨

The devDependency @semantic-release/git was updated from 7.0.15 to 7.0.16.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@semantic-release/git is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v7.0.16

7.0.16 (2019-07-01)

Bug Fixes

  • package: update globby to version 10.0.0 (a93b846)
Commits

The new version differs by 1 commits.

  • a93b846 fix(package): update globby to version 10.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of ember-cli is breaking the build 🚨

The devDependency ember-cli was updated from 3.12.0 to 3.13.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Custom modal name?

Hi, is it possible to customise the name used for the modal?

I like to store my modals in a nested directory structure (e.g: modals/some-modal). It seems that nested components is incompatible with the add-on?

An in-range update of @semantic-release/changelog is breaking the build 🚨

The devDependency @semantic-release/changelog was updated from 3.0.3 to 3.0.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@semantic-release/changelog is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v3.0.4

3.0.4 (2019-05-14)

Bug Fixes

  • package: update fs-extra to version 8.0.0 (50ed752)
Commits

The new version differs by 3 commits.

  • 50ed752 fix(package): update fs-extra to version 8.0.0
  • dd0d91f chore(package): update tempy to version 0.3.0
  • 00204d2 chore(package): update nyc to version 14.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of ember-cli-babel is breaking the build 🚨

The dependency ember-cli-babel was updated from 7.8.0 to 7.9.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli-babel is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for Release 7.9.0

πŸš€ Enhancement

Committers: 3

Commits

The new version differs by 15 commits.

  • 6b8cf74 Release 7.9.0
  • 8907a49 Update RELEASE.md.
  • a8adb49 Update modules API for colocation support (emberjs/rfcs#481). (#295)
  • 4f9e319 Update modules API for colocation support (emberjs/rfcs#481).
  • 0b5f299 Merge pull request #292 from babel/dependabot/npm_and_yarn/lodash.defaultsdeep-4.6.1
  • 909a94c Merge pull request #293 from babel/dependabot/npm_and_yarn/lodash.merge-4.6.2
  • 447b7b2 upgrade all in-range deps (#291)
  • e61f9b2 Bump lodash.merge from 4.6.1 to 4.6.2
  • dba1ec5 Bump lodash.defaultsdeep from 4.6.0 to 4.6.1
  • 47672e0 Merge pull request #289 from efx/remove-bower-config
  • adfd200 remove legacy bower configuration
  • 2714489 Merge pull request #288 from rwjblue/reroll-yarn
  • a61d5d3 Refresh yarn.lock.
  • a4a668b Merge pull request #287 from rwjblue/add-release-setup
  • 321743b Add automated release setup.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of ember-qunit is breaking the build 🚨

The devDependency ember-qunit was updated from 4.5.0 to 4.5.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-qunit is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v4.5.1

πŸ› Bug Fix

  • #528 Add a small configurable delay to test isolation validation assertion. (@rwjblue)

Committers: 2

Commits

The new version differs by 5 commits.

  • 46b7c68 Release 4.5.1
  • e808fb7 Add a small configurable delay to test isolation validation asse… (#528)
  • 9efa52e Add a small configurable delay to test isolation validation assertion.
  • f2109f9 Merge pull request #527 from emberjs/dependabot/npm_and_yarn/ember-resolver-5.2.0
  • c6fe6d0 Bump ember-resolver from 5.1.3 to 5.2.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @commitlint/config-conventional is breaking the build 🚨

The devDependency @commitlint/config-conventional was updated from 7.5.0 to 7.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@commitlint/config-conventional is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of husky is breaking the build 🚨

The devDependency husky was updated from 2.6.0 to 2.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

husky is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by commits ahead by 0, behind by 24.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Resolve multiple arguments not working

I have a modal with two text fields. After filling them up, when you click the YES
button, I call the action "resolve" with two arguments containing the two texts. In the .then((text1, text2) => ..., text2 is always undefined.

I've debugged the service, and in resolve action, arguments are good. But the call to this.resolve(...arguments) fails, because the function resolve only takes first argument as data, the second one is label, so it is resolved as label and not passed to the .then function later.

Captura de pantalla 2019-07-08 a las 10 05 35

Captura de pantalla 2019-07-08 a las 9 48 28

Captura de pantalla 2019-07-08 a las 9 48 47

Captura de pantalla 2019-07-08 a las 9 50 00

Captura de pantalla 2019-07-08 a las 9 50 38

An in-range update of eslint-plugin-node is breaking the build 🚨

The devDependency eslint-plugin-node was updated from 9.0.1 to 9.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 3 commits.

  • 7ce77f9 πŸ”– 9.1.0
  • e5aee3c πŸ› support * in engines.node (fixes #155)
  • fd9d19d ✨ no-deprecated-api adheres to targeted node version (fixes #141) (#164)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

onTransitionEnd can be triggered by child elements

I found out that transitionend event emitted from child element inside modal component can trigger modal to be prematurely close.
If I added a check in on-transition-end.js like so then it works. I'm not sure if the intention was to catch all transitionend event but it looks like a bug to me.

export default function onTransitionEnd(element, callback, transitionProperty = 'all', once = false) {
  const fn = (e) => {
    const { propertyName, type, target } = e;
    // Check to see if target and element are the same element.
    if (target !== element) {
      return ;
    }

    if (transitionProperty !== 'all' && propertyName !== transitionProperty) {
      return;
    }

    if (once) {
      element.removeEventListener(type, fn, true);
    }

    run(null, callback, e);
  };

  element.addEventListener(transitionEndEventName, fn, true);
}

An in-range update of ember-resolver is breaking the build 🚨

The devDependency ember-resolver was updated from 5.2.0 to 5.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-resolver is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for Release 5.2.1

v5.2.1 (2019-08-09)

πŸ› Bug Fix

  • #396 Component and their templates should be normalized the same. (@rwjblue)

Committers: 1

Commits

The new version differs by 5 commits.

  • cd2e16b Release 5.2.1
  • 307ce67 Add v5.2.1 to CHANGELOG.
  • 403bb72 Component and their templates should be normalized the same. (#396)
  • 422b1c7 Component and their templates should be normalized the same.
  • 6f9793b Bump eslint-plugin-ember from 6.7.1 to 6.8.2

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Populated model.options in computed property on Modal component?

Hello!

I have a computed property on a modal component.

The computed property creates a 'title' for the modal which I want to display in the modal template.
The title computed property is dependent on a value in the modal's options object (this value is the model for a form contained within the modal)

  title: computed('model.options.formModel', function() {
    if(this.get(model.options.formModel)) {
      alert('hello')
    }
  }

It seems that the options object is not populated when I try to read it using this.modal.options in the component.

I've tried waiting on model.promise in the hope that when the promise is resolved, the options become available, but no luck.

I've also tried making the computed dependent on model.options.@each and then check for this.model.options.formModel when this.model.options changes - but also no luck.

Any suggestion on how to go about accessing the options of a particular modal in a computed property of a modal component?

Cheers!

An in-range update of eslint-plugin-ember is breaking the build 🚨

The devDependency eslint-plugin-ember was updated from 6.2.0 to 6.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-ember is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v6.3.0

πŸš€ Enhancement

  • #369 Add new 'route-path-style' rule (@bmish)
  • #372 Add new 'no-unnecessary-index-route' rule (@bmish)
  • #262 Add new 'require-return-from-computed' rule (@gmurphey)
  • #378 Add new no-unnecessary-service-injection-argument rule (@bmish)

πŸ“ Documentation

  • #395 docs: improve closure-action rule examples (@Caltor)
  • #383 no-deeply-nested-dependent-keys-with-each: Fix documentation examples (@Alonski)

🏠 Internal

  • #386 test: add null output assertions for lint rules / test cases with no autofixer. (@bmish)

Committers: 4

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @commitlint/cli is breaking the build 🚨

The devDependency @commitlint/cli was updated from 7.5.2 to 7.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@commitlint/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of ember-export-application-global is breaking the build 🚨

The devDependency ember-export-application-global was updated from 2.0.0 to 2.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-export-application-global is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 2 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of ember-load-initializers is breaking the build 🚨

The devDependency ember-load-initializers was updated from 2.0.0 to 2.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-load-initializers is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for Release 2.1.0

πŸš€ Enhancement

πŸ“ Documentation

🏠 Internal

Committers: 4

Commits

The new version differs by 92 commits.

  • a28db5e Release 2.1.0
  • 60d700d Add release-it setup.
  • fae7eab Build(deps): Bump ember-cli-babel from 7.9.0 to 7.10.0
  • 8277efa Merge pull request #111 from ro0gr/types
  • 74ad062 Add typescript support
  • 01b3b93 Build(deps-dev): Bump eslint-plugin-ember from 6.9.1 to 6.10.0
  • 4b1da73 Build(deps-dev): Bump eslint-plugin-ember from 6.9.0 to 6.9.1
  • 72d274a Build(deps): Bump ember-cli-babel from 7.8.0 to 7.9.0
  • 84e0ab2 Build(deps-dev): Bump eslint-plugin-ember from 6.8.2 to 6.9.0
  • 4fece24 Build(deps-dev): Bump ember-qunit from 4.5.0 to 4.5.1
  • d42dc0d Build(deps-dev): Bump ember-resolver from 5.2.0 to 5.2.1
  • ae9616b Build(deps-dev): Bump eslint-plugin-ember from 6.7.1 to 6.8.2
  • fd20863 Build(deps-dev): Bump ember-resolver from 5.1.3 to 5.2.0
  • 3843070 Build(deps-dev): Bump ember-qunit from 4.4.1 to 4.5.0
  • d66c66e Build(deps): [Security] Bump lodash from 4.17.11 to 4.17.14

There are 92 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of qunit-dom is breaking the build 🚨

The devDependency qunit-dom was updated from 0.9.0 to 0.9.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

qunit-dom is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v0.9.1

πŸš€ Enhancement

🏠 Internal

Committers: 4

Commits

The new version differs by 116 commits.

  • e797234 v0.9.1
  • d844878 build(deps-dev): bump eslint-config-prettier from 6.4.0 to 6.5.0 (#517)
  • d4e4307 build(deps-dev): bump rollup from 1.25.2 to 1.26.0 (#516)
  • a03f613 build(deps-dev): bump @types/jest from 24.0.19 to 24.0.20 (#515)
  • 8545c51 build(deps-dev): bump @ember/optional-features from 1.0.0 to 1.1.0 (#513)
  • d27f0e1 build(deps-dev): bump rollup from 1.25.1 to 1.25.2 (#514)
  • 2246477 build(deps-dev): bump rollup from 1.24.0 to 1.25.1 (#512)
  • 4a0374f build(deps-dev): bump ember-cli-htmlbars from 4.0.5 to 4.0.8 (#511)
  • b9c7d2a build(deps-dev): bump rollup from 1.23.1 to 1.24.0 (#510)
  • 06ef888 build(deps-dev): bump @types/jest from 24.0.18 to 24.0.19 (#509)
  • afca4ec build(deps-dev): bump typescript from 3.6.3 to 3.6.4 (#507)
  • 738e9b6 build(deps-dev): bump ember-cli-inject-live-reload from 2.0.1 to 2.0.2 (#506)
  • 212cd7c build(deps-dev): bump ember-source from 3.13.2 to 3.13.3 (#505)
  • 2dfb164 Merge pull request #499 from step2yeung/hasnotext
  • 058b20d Add hasNoText assertion

There are 116 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of babel-eslint is breaking the build 🚨

The devDependency babel-eslint was updated from 10.0.2 to 10.0.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

babel-eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 2 commits.

  • 183d13e 10.0.3
  • 354953d fix: require eslint dependencies from eslint base (#794)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.