Description
Debugging requests today is painful because logs don’t provide enough context. Adding better metadata to logs and responses will help developers and agents quickly identify issues, cache status, and request paths. We lack structured data to trace performance, caching, and errors at the HTML/component level. Introducing standardized attributes and richer error data will improve monitoring and debugging experiences.
Proposed changes
- Add the section path to
/deco/render routes, e.g.:
GET /deco/render/sections/Product/Shelf.tsx instead of /deco/render?props={}.
- Add a warning log for
/deco/render requests that are not cached yet possible.
- Implementation of a debugger on client side
- Send metadata to the client to surface loader timing, cache status, and similar metadata.
- Attach stack traces and contextual info when errors occur (where the error originated, section path, etc.).
- Expose cache and timing information consistently across rendered responses.
- Log the request path in all error logs across the system.
Description
Debugging requests today is painful because logs don’t provide enough context. Adding better metadata to logs and responses will help developers and agents quickly identify issues, cache status, and request paths. We lack structured data to trace performance, caching, and errors at the HTML/component level. Introducing standardized attributes and richer error data will improve monitoring and debugging experiences.
Proposed changes
/deco/renderroutes, e.g.:GET /deco/render/sections/Product/Shelf.tsxinstead of/deco/render?props={}./deco/renderrequests that are not cached yet possible.