Skip to content
#

microservices

Here are 677 public repositories matching this topic...

express-gateway
XVincentX
XVincentX commented Jan 2, 2018

If not for some particular exceptions, the status code returned from our WebAPI on error is always 500, regardless of the kind of error.

If an object already exists, for example, it should be returned as 409. If the object does not pass the schema validation, it should be a 415.

Go through the whole WebAPI and verify that the status codes are being returned correctly.

Hint: Error cl

NodeBootstrap - generates skeleton project for Node/Express.js with pre-configured best-practices. Kick-start your Node project development with tons of boilerplate taken care of, such as: clustering, Docker-support, database migrations, automated testing, error-handling, modularity, advanced logging, templated views, environments etc.

  • Updated Jul 21, 2020
  • JavaScript
lucas-rudd
lucas-rudd commented Feb 18, 2020

Right now, when you archive a key, you can only see it if you manually search for it.

This can cause some key name conflict issues, or issues when trying to create a folder with the same name as an archived (bu not yet deleted key).

It would be ideal for there to be a way to see all archived keys at once, without the need to search for them in the search bar.

Improve this page

Add a description, image, and links to the microservices topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the microservices topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.