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

New error popping up when serving the editor locally #528

Open
RyanCoulsonCA opened this issue Jan 24, 2025 · 0 comments
Open

New error popping up when serving the editor locally #528

RyanCoulsonCA opened this issue Jan 24, 2025 · 0 comments
Labels
Priority: Low This task can is low priority and can wait if high priority tasks exist RAMP Work that should go back to RAMP Proper, or work specific to RAMP itself

Comments

@RyanCoulsonCA
Copy link
Member

RyanCoulsonCA commented Jan 24, 2025

Description

When running the editor locally via npm run dev, I'm getting the following error:

[vite] warning: <tr> cannot be child of <table>, according to HTML specifications. This can cause hydration errors or potentially disrupt future functionality

It's showing up for a few files (metadata-editor.vue, dynamic-editor.vue, home.vue), presumably any file that is using the table HTML element.

The error seems to have started popping up after we merged in the PR upgrading RAMP to v4.10.2, but nothing in that PR changes anything relating to this (except updating package-lock.json, so maybe some other library update has done this).

We should look into why this is showing up now. If we can't figure out how to get rid of the error, this can apparently be fixed by wrapping the <tr> element with <tbody> as such:

<table>
  <tbody>
    <tr>...</tr>
  </tbody>
</table>
@RyanCoulsonCA RyanCoulsonCA added the Priority: Low This task can is low priority and can wait if high priority tasks exist label Jan 24, 2025
@szczz szczz added the RAMP Work that should go back to RAMP Proper, or work specific to RAMP itself label Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low This task can is low priority and can wait if high priority tasks exist RAMP Work that should go back to RAMP Proper, or work specific to RAMP itself
Projects
None yet
Development

No branches or pull requests

2 participants