Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / AqoviaElements/properties-from-ancestor-behavior issues and pull requests
#21 - Polymer v3 support
Issue -
State: open - Opened by ma499 about 6 years ago
#20 - Pull to V2 all improvements added 'backwards compatibly' to V1
Pull Request -
State: closed - Opened by slawomir-brzezinski-at-interxion about 6 years ago
#19 - For Polymer 1.X - Fix builds in travis - update node 6.0->8.0 and semver-stabilize dev dependencies, so maybe they won't change the required node version anymore
Pull Request -
State: closed - Opened by slawomir-brzezinski-at-interxion about 6 years ago
#18 - Fix builds in travis - update node 6.0->8.0 and semver-stabilize dev dependencies, so maybe they won't change the required node version anymore
Pull Request -
State: closed - Opened by slawomir-brzezinski-at-interxion about 6 years ago
#17 - Fix #15 - Boolean 'false on ancestor, but true directly' results in false
Pull Request -
State: closed - Opened by slawomir-brzezinski-at-interxion about 6 years ago
#16 - Allow Continuous Integration (Travis) to create 1.0 releases
Pull Request -
State: closed - Opened by slawomir-brzezinski-at-interxion about 6 years ago
#15 - Corner Case - When ancestor doesn't have the boolean attribute but the child does, the property shows as false
Issue -
State: closed - Opened by zlamma about 6 years ago
Labels: bug
#14 - Address Issue #13 - Corner case memory leak - when behavior used many times on same element and element gets detached
Pull Request -
State: closed - Opened by zlamma about 7 years ago
- 1 comment
#13 - Corner case memory leak - when behavior used many times on same element and element gets detached
Issue -
State: closed - Opened by zlamma about 7 years ago
Labels: bug
#12 - Address Issue #6 - Add support for different attribute/property name in ancestor
Pull Request -
State: closed - Opened by zlamma over 7 years ago
- 3 comments
#11 - Address Issue #10 - Polymer 2.0 version - using a hybrid (non-class) behavior
Pull Request -
State: closed - Opened by slawomir-brzezinski-at-interxion over 7 years ago
#10 - Build a Polymer 2.0 version
Issue -
State: closed - Opened by zlamma over 7 years ago
Labels: enhancement
#9 - Address Issue #8 - Add support for receiving a boolean that is initially false
Pull Request -
State: closed - Opened by slawomir-brzezinski-at-interxion over 7 years ago
- 4 comments
#8 - Add support for receiving a boolean that is initially false (e.g. get notified about <fieldset disabled>)
Issue -
State: closed - Opened by slawomir-brzezinski-at-interxion over 7 years ago
Labels: enhancement
#7 - Add support for upward data flow - changing the ancestor value by changing the property in descendant
Issue -
State: open - Opened by zlamma over 7 years ago
Labels: enhancement
#6 - Add support for different attribute/property name in ancestor
Issue -
State: closed - Opened by zlamma over 7 years ago
Labels: enhancement
#5 - Fix Issue #4 - respect attribute deserialization logic (when ancestor is pure HTML)
Pull Request -
State: closed - Opened by zlamma over 7 years ago
Labels: enhancement
#4 - When reading from attribute, need to respect property type's deserialization rules
Issue -
State: closed - Opened by slawomir-brzezinski-at-interxion over 7 years ago
- 2 comments
Labels: bug
#3 - Fix #2 - Corner case: 'Singleton variables' cause corruption in change handling
Pull Request -
State: closed - Opened by slawomir-brzezinski-at-interxion over 7 years ago
#2 - Corner case: 'Singleton variables' cause corruption in change handling (only affects use cases with many components of the same type in many ancestors) - instances start taking value from the last initialized ancestor
Issue -
State: closed - Opened by slawomir-brzezinski-at-interxion over 7 years ago
- 2 comments
#1 - First Implementation of properties-from-ancestor-behavior
Pull Request -
State: closed - Opened by slawomir-brzezinski-at-interxion over 7 years ago