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

Port to Polymer 1.x #16

Merged
merged 7 commits into from
Feb 8, 2017
Merged

Port to Polymer 1.x #16

merged 7 commits into from
Feb 8, 2017

Conversation

bergie
Copy link
Member

@bergie bergie commented Feb 8, 2017

@jonnor
Copy link
Member

jonnor commented Feb 8, 2017

@bergie whats the status? Mostly working or not? Any limitations, or blockers?

@bergie
Copy link
Member Author

bergie commented Feb 8, 2017

@jonnor working fully. Tests passing on both Chrome and PhantomJS

@jonnor
Copy link
Member

jonnor commented Feb 8, 2017

Ok. If we're gonna merge this, then this means bumping major version, since incompatible with old Polymer. Maybe go 1.x to match?

@bergie
Copy link
Member Author

bergie commented Feb 8, 2017

In this case the component migration to 1.x was simply done with https://github.com/PolymerLabs/polyup

The only manual tweak was to change the notify setting to prevent unwanted events from firing 6364a67

For something like noflo-ui there will likely be CSS changes also needed

@bergie
Copy link
Member Author

bergie commented Feb 8, 2017

@jonnor yes, major bump sounds reasonable

@bergie bergie merged commit 30d3226 into master Feb 8, 2017
@bergie bergie deleted the polymer_1 branch February 8, 2017 14:39
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