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

Interactivity API: Debug - Warning about Server Directives Processing errors. #60035

Closed
cbravobernal opened this issue Mar 20, 2024 · 7 comments
Labels
Developer Experience Ideas about improving block and theme developer experience [Feature] Interactivity API API to add frontend interactivity to blocks. [Type] Enhancement A suggestion for improvement.

Comments

@cbravobernal
Copy link
Contributor

What problem does this address?

Right now, if there is an error during the server directives processing, there is no way to determine that the error occurred. There is only a layout shift (a brief screen flash) when loading the website, and if the developer has a fast connection or a fast local environment, it is really hard to notice.

What is your proposed solution?

If debugging is enabled, the client could send a console error if the source differs from the virtual DOM, or the server could send a PHP warning notice if the server directive processing is aborted (due to malformed HTML or unsupported tags).

@cbravobernal cbravobernal added [Type] Enhancement A suggestion for improvement. [Feature] Interactivity API API to add frontend interactivity to blocks. Developer Experience Ideas about improving block and theme developer experience labels Mar 20, 2024
@gziolo gziolo added the Needs Dev Ready for, and needs developer efforts label Mar 26, 2024
@fabiankaegy
Copy link
Member

Really looking forward to this :) Currently, it is really hard to debug what's causing the server processing to fail.

@sirreal
Copy link
Member

sirreal commented Apr 15, 2024

_doing_it_wrong around here may be a good start.

@cbravobernal
Copy link
Contributor Author

I just created a PR for it in wordpress-develop.

WordPress/wordpress-develop#6413

@cbravobernal cbravobernal added Needs Testing Needs further testing to be confirmed. and removed Needs Dev Ready for, and needs developer efforts labels Apr 23, 2024
Copy link

Hi,
This issue has gone 30 days without any activity. This means it is time for a check-in to make sure it is still relevant. If you are still experiencing this issue with the latest versions, you can help the project by responding to confirm the problem and by providing any updated reproduction steps.
Thanks for helping out.

@github-actions github-actions bot added the [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. label May 24, 2024
@sirreal
Copy link
Member

sirreal commented May 24, 2024

It's being worked on, good bot.

@sirreal sirreal removed the [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. label May 24, 2024
@gziolo
Copy link
Member

gziolo commented Jun 13, 2024

That seems to be resolved now. Is the anything left to do?

@cbravobernal
Copy link
Contributor Author

I think everything is done.

@cbravobernal cbravobernal removed the Needs Testing Needs further testing to be confirmed. label Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Developer Experience Ideas about improving block and theme developer experience [Feature] Interactivity API API to add frontend interactivity to blocks. [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

4 participants