Use 2.0 #3
Merged
Use 2.0 #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
valdrinkoshi
force-pushed
the
use-2.0
branch
from
0776c3b to
34e344c
Compare
|
@cdata PTAL (don't get scared of the big changes 🍰 ) |
valdrinkoshi
force-pushed
the
use-2.0
branch
from
34e344c to
2b061c3
Compare
valdrinkoshi
force-pushed
the
use-2.0
branch
from
43dee0b to
dc2061d
Compare
valdrinkoshi
force-pushed
the
use-2.0
branch
from
739a477 to
58aa499
Compare
valdrinkoshi
force-pushed
the
use-2.0
branch
from
58aa499 to
8ddc49c
Compare
valdrinkoshi
force-pushed
the
use-2.0
branch
from
b7f8335 to
3c684ab
Compare
valdrinkoshi
force-pushed
the
use-2.0
branch
from
64c2bc3 to
6b210da
Compare
valdrinkoshi
force-pushed
the
use-2.0
branch
from
0686782 to
e7fccd0
Compare
…aching renderer. Update to demo & test shadydom
valdrinkoshi
force-pushed
the
use-2.0
branch
from
17db7c5 to
ef0ed9d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The main change is moving to Polymer 2.0, which allows using es6 classes and the new templatizer (which removes the need mirroring properties to the renderer and just use the data binding system 🎉 )
Also:
<body>if no-one prevents the attach/detach eventsiron-overlay-container, which makes it optional)noCancelOnOutsideClickwill be skipped, overlay below it (if any) will handle thetapeventrendererpublic readonly property (fixes overlay should exposerendererproperty #4)iron-animated-overlay(and renderer) intoiron-overlay, added propertyanimatedCurrently in ShadyDom the renderer is not rendered correctly because of webcomponents/shadycss#17