Skip to content

Conversation

@ionphractal
Copy link

I found a more explicit way without using the store (respectively creating a new one). The $parent object is the right scope to set value for isSubmitting which will then be used in the mixin.

Still have to test this a little but I wanted to know your thoughts on this. @roschaefer @appinteractive @mimicc83

fixes #300
closes #301

@appinteractive
Copy link
Member

Please do NOT use the $parent scope!!! That’s really bad practice and can lead to bad sideeffects. Use the $emit method to dispatch an event and catch it explicitly on the parent.

@appinteractive appinteractive self-requested a review October 2, 2018 09:16
Copy link
Member

@appinteractive appinteractive left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please do NOT use $parent but $emit or equal to maintain component encapsulation

@ionphractal
Copy link
Author

Something learned again.

@ionphractal ionphractal closed this Oct 2, 2018
@ionphractal ionphractal deleted the contribution-draft-confirmation branch October 2, 2018 17:02
@appinteractive
Copy link
Member

Hey why did you deleted the pr completely?

@ionphractal
Copy link
Author

Well, I found it to be junk (the history is still here for reference for everyone to see) and rewrote it from scratch. And I wanted to re-use the branch for it, so had to delete it anyway as I don't like force push as long as I can avoid it. Force push would've probably messed up the history here. This is the new one I opened for this: #311

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

Successfully merging this pull request may close these issues.

Remove "Draft" Dialog when saving contribution

2 participants