blenderskool / diode Goto Github PK

For cached responses that contain a Transfer-encoding header, the following error is thrown when a cache hit is made:

Parse Error: Content-Length can't be present with Transfer-Encoding

Proxy URLs generated in Diode right now are not human-readable and don't have any context about what the API endpoint actually does.
This can be improved by updating the proxy URL id to include the route name entered by the user.

Example:
{route-name encoded in a URL friendly way}-{nanoid of a shorter length}
In this case, the route name cannot be changed once it's created.

This can help in preventing public Diode URLs from being used to access unintended data from the origin endpoint.
In this case, only those query params and headers specified in the Diode dashboard will be forwarded, the rest ignored.

• nvm run dev/start doesn't work gives error:

digital envelope routines::unsupported  

use node v16.19.1 to run npm-script

• npx prisma db push doesn't work giving error

Unknown binaryTarget debian-openssl-3.0.x and no custom binaries were provided error Command failed with exit code 1

need to update the dependency for prisma-cli and @prisma/client to above v3.13.0.

A duplicate option can be added to API Route which would open a modal with an input field to take the name for the new API route being created.
This input field can have a default value of {name of API route being duplicated} Duplicate.
Complete configuration should be duplicated.

Calls to endpoints that don't exist on the database fail with status code 500.
The issue is that results from findUnique queries are not checked for null values.

Additional areas to check:

• Invalid Project page
• Invalid API route page

Dangerous actions that involve deletion of some stuff should show a confirmation dialog to the user before the deletion operation is performed.

While Chakra-UI already has Alert dialog components that can be used, it's not very ergonomic to use out of the box.
Since this will be a fairly consistent component used in many places, we can maybe abstract the implementation details into something as simple as window.confirm style call.

Middleware that provides basic partial querying and filtering capabilities for APIs that respond with JSON data.
There isn't any popular standard for this, json-mask package seems like a good start.
Instead of using fields query parameter for this, maybe something else can be used to prevent any conflict with origin endpoint.

A point to note is that this middleware does consume the data that is received by the origin endpoint, unlike the existing middlewares.
So it definitely would be slower to use this approach instead of using partial query on the origin endpoint itself(i.e. if origin endpoint supports it)

Potential flow with this and other middlewares:

• Receive request
• Restriction
• Rate Limiter
• Cache GET
• Origin hit
• Partial JSON query
• Cache PUT
• Send response

Users should be able to create accounts and create projects associated with that account.

Input fields can render the Secrets referenced slightly differently similar to how Postman does it.