Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calling set on destroyed object #41

Open
sir-dunxalot opened this issue Aug 16, 2015 · 4 comments
Open

Calling set on destroyed object #41

sir-dunxalot opened this issue Aug 16, 2015 · 4 comments

Comments

@sir-dunxalot
Copy link
Owner

Update input group actions to:

actions: {

    showError: function showError() {
      if (!this.get('isDestroying')) {
        this.set('showError', true);
      }
    },

    setGroupAsInvalid: function setGroupAsInvalid() {
      if (!this.get('isDestroying')) {
        this.set('isValid', false);
      }
    },

    setGroupAsValid: function setGroupAsValid() {
      if (!this.get('isDestroying')) {
        this.set('isValid', true);
      }
    }

  },
@jme783
Copy link

jme783 commented Mar 4, 2016

+1, implemented this fix on our fork and it worked

@sir-dunxalot
Copy link
Owner Author

Awesome, thanks for the update. I will try and release this as a patch soon (and before 1.0.0 of this library is released as stable for Ember 2+).

@jme783
Copy link

jme783 commented Mar 4, 2016

Cool thx @sir-dunxalot! FYI @brycekahle and myself have been working on a fork of this library that is compatible with Ember 2.4+. The fork is here --> https://github.com/spark/ember-easy-form-extensions.

We would definitely love to submit some P/Rs if you'd be interested

@sir-dunxalot
Copy link
Owner Author

Oh awesome, thanks for the heads. Up 2.0.0 is now released because Ember EasyForm now has a 1.0.0.rc-1 release. The 2.0.0 release gets back to the original purpose of this addon, which is handling submission events (not form components).

If you're looking to keep using the components I'd be open to making additional 1.x releases that also support Ember 2.0+. And any other changes you made that still relate to 2.0 can definitely be merged into master.

Let me know what you think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants