dev-proxy
dev-proxy copied to clipboard
microsoft
Dev Proxy is an API simulator that helps you effortlessly test your app beyond the happy path.
Now that we aligned versioning schemas with proxy versions, we should show a warning when the user tries to load a config file that uses a schema with a different...
> VS Code will use the standard description field from the [JSON Schema specification](https://json-schema.org/specification) in order to provide information about properties on hover and during autocomplete. > If you want...
Currently (like in many other configure cases) if we want to setup some custom or predefined plugin to the proxy we need to modify the `devproxyrc.json`. This seems kinda hacky...
### Description It seems that the **AzureCliCredential** in the `Azure.Identity` nuget package. No longer works when the proxy is running. [here](https://github.com/svrooij/m365-proxy-auth-issue) is the code to validate. ### Expected behaviour I...
In a fashion similar to showing least-required permissions, allow for showing the claims that are in the provided access token. Information that matches the jwt.ms page.
A neat feature would be to use the mock feature with a tool like [fakerjs](https://fakerjs.dev/api/) and essentially be able to mock a full API, and generate random data. For instance...
Now that we've got schema for the config and the mocks file, we should look into using them to validate the files and catch error early, providing users with information...
Related to #8 Extend the retry-after plugin with support for batching. When processing the request, if it's a batch, process the requests in its body and see if any of...
For requests passed through to Graph, capture requests that failed due to lack of permissions. Use the Dev API to check which permissions are necessary and show a meaningful error...