Frontmatter
| id | 6090 |
| title | core.Base, component.Base: allow unregistering existing components |
| state | Closed |
| labels | enhancement |
| assignees | tobiu |
| createdAt | Nov 7, 2024, 9:36 PM |
| updatedAt | Nov 7, 2024, 9:41 PM |
| githubUrl | https://github.com/neomjs/neo/issues/6090 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Nov 7, 2024, 9:41 PM |
core.Base, component.Base: allow unregistering existing components
tobiu assigned to @tobiu on Nov 7, 2024, 9:36 PM
tobiu
Nov 7, 2024, 9:41 PM
wrong commit message, apologies.
the ticket got resolved via: https://github.com/neomjs/neo/commit/7d3a8dcf31e725c3a1605a48bc874df29805a754
tobiu closed this issue on Nov 7, 2024, 9:41 PM
advanced feature for devs who know what they are doing.
example: component based list with index based items => when adding new items or sorting, it can happen that ids get moved around. in this context it can briefly happen that ids are no longer unique until the sync OP is done.
the framework should not restrict it.