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

feat: provides collection based append/remove methods for Node #14204

Conversation

MarcinVaadin
Copy link
Member

@MarcinVaadin MarcinVaadin commented Jul 22, 2022

Description

Added Collection based appendChild / appendVirtualChild / insertChild / removeChild / removeVirtualChild methods for com.vaadin.flow.dom.Node

Fixes #13599

Type of change

  • Bugfix
  • Feature

Checklist

  • I have read the contribution guide: https://vaadin.com/docs/latest/guide/contributing/overview/
  • I have added a description following the guideline.
  • The issue is created in the corresponding repository and I have referenced it.
  • I have added tests to ensure my change is effective and works as intended. already covered with tests
  • New and existing tests are passing locally with my change.
  • I have performed self-review and corrected misspellings.

Additional for Feature type of change

  • Enhancement / new feature was discussed in a corresponding GitHub issue and Acceptance Criteria were created.

@MarcinVaadin MarcinVaadin linked an issue Jul 22, 2022 that may be closed by this pull request
@sonarcloud
Copy link

sonarcloud bot commented Jul 22, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@github-actions
Copy link

Unit Test Results

   904 files  +107     904 suites  +107   58m 28s ⏱️ + 12m 24s
5 894 tests +  64  5 850 ✔️ +  91  44 💤 +1  0  - 7 
6 119 runs  +219  6 069 ✔️ +241  50 💤 +6  0  - 7 

Results for commit e2d96be. ± Comparison against base commit 4e62c04.

}

/**
* Removes the given child element(s).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not exactly sure, but I guess now that these new APIs are accepting a collection it is fine to just use the plural without parenthesis:

Suggested change
* Removes the given child element(s).
* Removes the given child elements.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Collection may contain only one element, so probably that's fine to say "element(s)"

@mshabarov mshabarov self-requested a review July 25, 2022 11:22
@mshabarov mshabarov merged commit 42f14cb into master Jul 28, 2022
@mshabarov mshabarov deleted the issues/13599-provide-collection-based-appendremove-methods-for-node-2 branch July 28, 2022 10:29
@vaadin-bot
Copy link
Collaborator

This ticket/PR has been released with Vaadin 23.2.0.beta1 and is also targeting the upcoming stable 23.2.0 version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Provide collection based append/remove methods for Node
4 participants