from polymerelements to PolymerElements in 2.0-preview #133
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
added a commit
that referenced
this pull request
May 13, 2017
* port to 2.0 * update repos links * update deps * use only slot * webanimations as devDep * more descriptive tests. Make passive: false explicit. * use variants * revert type for animation configs * revert setting of sizingTarget, should be done in attached * remove not used animation * use neon-animation 2.0-preview also in the 1.x variant * use neon-animation/web-animations.html * resolutions * update deps and resolutions * Depend on test-fixture v2 * auto-generated: update repo for v2 * remove flush as shadydom#56 got fixed * update deps * update deps * Point to Polymer 2.0 RC 1 * Update travis config * Keep list of scroll events * named slot * use only slots * [skip ci] assigned to the slot * remove test-fixture dependency * update readme * query for content and slot, skip non-elements * Update travis config (#136) * from polymerelements to PolymerElements in 2.0-preview (#133) * Consistent use of CamelCase in bower dependencies * made the "variants 1.x" section consistent as well
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.
This pull request wants to make this Polymer element consistent with the majority of other Polymer elements in the 2.0-preview branch. The uppercase version "PolymerElements" is closer to real name of the github project name, like presented in the git URL.
The use of mixed case does not seem to have an effect on bower and JavaScript projects. But other languages like Java are more picky and would benefit from consistency.
I fixed this in the "2.0-preview" branch of this element, because it would be very nice to have this cleaned up and consistent in 2.0 release. I have manually checked 66 elements that have a "2.0-preview" branch. 56 are ok. This element is one of 10 which has these small differences
I'm mostly concerned with the bower "Main" dependencies, but as I have changed this file already I also fixed this in the devDependencies
This pull request is a manual follow up of PolymerLabs/tedium#47 and PolymerLabs/tedium#48 which try to do this in an automated way, but are stuck.