Extension for request tracing

[Igor Shadurin]

As our application grows in complexity, the need for robust debugging tools becomes increasingly apparent. We've noticed that there are instances where problems occur with accounts or files, and we aren't able to pinpoint exactly where these issues originate.

To enhance our debugging capabilities, it would be beneficial to extend the functionality of fdp-storage to trace the requests it makes. This feature would provide visibility into the data sent with each request, giving us the ability to identify where exactly account or file issues are happening.

This feature could be implemented in the form of a Chrome extension, similar to how Redux Debugger works, or through some other means that fits within our technical architecture. The goal is to have a mechanism that helps us better understand the interactions between fdp-storage and the rest of our application, thus improving our ability to diagnose and fix problems.

Acceptance Criteria:

• Implement an extension or tool that traces requests made by fdp-storage.
• The tool should provide visibility into the data sent with each request.
• The tool should be user-friendly and integrate seamlessly with our existing development workflow.

This issue is open for discussion, and we welcome any suggestions for the most effective way to implement this feature. Our aim is to make our debugging process more efficient, helping us to maintain the high quality of our application as it continues to evolve.