Feature Request: Chrome Extension for Improved Fetch Request Debugging

[kpidoff]

Description: I would like to propose the creation of a Google Chrome extension that simplifies the display of Fetch requests sent to the server. Currently, when using libraries like React Query, the queryKey is used to identify requests, which can be challenging to read during debugging. This extension would enhance the debugging experience by providing a more user-friendly and informative representation of Fetch requests in the DevTools Network tab.

Features:

• Display Fetch requests in a more readable format, including relevant request details, headers, and response data.
• Option to name or label Fetch requests for easier identification and debugging.
• Compatibility with popular libraries and frameworks (e.g., React Query) to seamlessly integrate with existing projects.
• Ability to filter and search for specific Fetch requests based on their names or labels.
• Support for inspecting and copying request/response data for further analysis.

Use Case: Developers often struggle with the readability and identification of Fetch requests, especially when working with complex applications or libraries. This extension would address this pain point and improve the overall development workflow by simplifying the debugging process.

Additional Information: Creating such an extension could greatly benefit developers who rely on Fetch requests for data retrieval and API interactions. It would make debugging more efficient and enjoyable, ultimately enhancing the developer experience in Chrome.

Please let me know if this feature request aligns with your goals, and if you have any questions or suggestions regarding its implementation.

[ymc9]

Awesome! Thanks for filing this with such detailed description!

[kpidoff]

That's normal, your project really means a lot to me.

[rortan134]

Just an opinion but although I do see the use for the chrome extension, I just think that it just couldn't possibly become relevant enough as to be worth the time it would take to get it done. Definitely one of those features to be done by a contributor (bounty?) or during spare time.

[ymc9]

Just an opinion but although I do see the use for the chrome extension, I just think that it just couldn't possibly become relevant enough as to be worth the time it would take to get it done. Definitely one of those features to be done by a contributor (bounty?) or during spare time.

I agree it doesn't need to be in the core part of ZenStack. A community package sounds like a good fit. It'd be great if some people who like ZenStack and are experienced with Chrome extension building can find the feature request here and make a contribution 😄!