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

Add dirty workaround for AST plugins in wrong order #16

Conversation

simonihmig
Copy link
Contributor

@cibernox As I wanted to update to the latest ember-in-element-polyfill, but without having to migrate away from ember-maybe-in-element, I took a look at the failing issue in #15 we talked about a while ago.

I remembered that I had to do some trickery regarding the order of AST plugins for an older version of the polyfill, where it had some explicit support for ember-maybe-in-element: https://github.com/kaliber5/ember-in-element-polyfill/blob/9aeec71d12dd6db9586097ffc11f94d30d6120cb/index.js

Applying the same tricks here seems to fix the issue!

And I certainly agree that this look ugly as hell, sorry about that! 😬

@simonihmig
Copy link
Contributor Author

Btw, this PR is targeting the feature branch of #15, adding an additional commit. Just to be clear!

@cibernox cibernox merged commit 0b4c390 into DockYard:use-new-in-element-polyfill Jun 29, 2019
@cibernox
Copy link
Contributor

@simonihmig sorry for the delay, I've been detoxing from the computer. Merged!

@cibernox
Copy link
Contributor

cibernox commented Jul 8, 2019

@simonihmig I came back today from holidays and I tested this but sadly it doesn't seem to work when installed in an addon: cibernox/ember-basic-dropdown#476

0.3.0 contains your changes. 0.4.0 is a re-publish of 0.2.0 reverting your changes.

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.

2 participants