Frontmatter
| id | 4683 |
| title | component.Base: explore & fix inconsistencies between the mounted state & having a vnode |
| state | Closed |
| labels | enhancementstale |
| assignees | [] |
| createdAt | Aug 9, 2023, 3:35 PM |
| updatedAt | Sep 13, 2024, 4:29 AM |
| githubUrl | https://github.com/neomjs/neo/issues/4683 |
| author | tobiu |
| commentsCount | 3 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Sep 13, 2024, 4:29 AM |
component.Base: explore & fix inconsistencies between the mounted state & having a vnode
tobiu
Aug 9, 2023, 3:39 PM
hmm, actually there is one exception: you can render a component (creating a vnode) without mounting it. but as soon as we come into the update cycle, the assumption is correct.
bigger question: do we even need render without mounting.
@github-actions - 2024-08-29T02:26:48Z
This issue is stale because it has been open for 90 days with no activity.
- 2024-08-29T02:26:49Z @github-actions added the
stalelabel
@github-actions - 2024-09-13T02:29:18Z
This issue was closed because it has been inactive for 14 days since being marked as stale.
- 2024-09-13T02:29:18Z @github-actions closed this issue
we can most likely simplify this a lot, in case we use the assumption: if a component has a vnode (real DOM), it has to be mounted.
then we could use
afterSetVnode()as the single source of truth to change the value of the mounted config.