You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
It'd be fantastic if there could be an exposed cache of parsed RAML. It'd be a breaking change to the API, but it'd enable much more performant and flexible solution using the RAML parser. For example, having the API designer re-parse every change, generating documentation from a watch server, automatically restarting Osprey during development, etc. Also, it'd fix making multiple requests to the same file on the filesystem or remotely and properly allow composition using the filesystem instead of raml globals.
Existing example: Browserify + watchify
The text was updated successfully, but these errors were encountered:
It'd be fantastic if there could be an exposed cache of parsed RAML. It'd be a breaking change to the API, but it'd enable much more performant and flexible solution using the RAML parser. For example, having the API designer re-parse every change, generating documentation from a watch server, automatically restarting Osprey during development, etc. Also, it'd fix making multiple requests to the same file on the filesystem or remotely and properly allow composition using the filesystem instead of raml globals.
Existing example: Browserify + watchify
The text was updated successfully, but these errors were encountered: