Currently, closing the browser results in a loss of the generated OpenAPI specification data. To enhance usability and continuity, could we consider the following features?
Implementing a session save feature that allows users to pause and resume their recording sessions at a later time.
Providing an option to upload a JSON file of a previously downloaded OpenAPI specification, enabling users to continue recording from where they left off.
For some of these features, it may make sense to incorporate a server-side component. For example, sending captured data to be trained (7) or cross-referencing with existing documented APIs based on the host names (3).
Would it be possible to opt-in always running the extension on the background, so that you don't need to worry about profiling a specific website, and just passively collect all API's you've accessed?
Might be relevant when you've lost access to a front (or if the front gets taken down) and you'd like to directly communicate with the API.
Awesome work! I have one feature request though - could it record auth headers/tokens? This would be super useful for logging which requests require authorization and how to send an authorized request