codever VS express-openapi-validator

As mentioned How I manage my dev bookmarks to save time and nerves I use heavily Codever to manage my bookmarks and code snippets, so there is always a browser tab open with the website. Lately I've also been developing quite a bunch of new features on the project. Lots of testing happens in the browser, and until now there was no quick way to differentiate between the production and development version, unless I look at the URL in the browser's navigation bar of course.

Project: codever

Project: codever - File: snippet-details.component.html

At Codever we use Angular extensively, and many time the use navigates to certain routes where dynamically content based on an id for example is loaded. To access these path params in angular navigation you have two possibilities.

In Codever we use extensively the Angular Http Client to make REST calls against a NodeJs/ExpressJS API - source code on Github.

When you are searching your code snippets on Codever, depending on the search terms you use, relevant results are displayed. Behind this there is a MongoDb full text search index. Let's see how it is created and used.

I've been using Visual Studio Code for some projects lately, so I made it easy now to save and search code snippets on Codever directly from Visual Studio Code via the Codever Snippets VSCode Extension.

Project: bookmarks.dev - File: snippet-form.base.component.ts

If you have found this useful, please show some love and give us a star on Github

The build step is where I put all of them together, which is the messy and tricky part. Although not directly related to your question, I also use this validation tool to handle request validation based on my result yml.

express-openapi-validator Express middleware that routes and validates requests according to an OpenAPI spec.

The express-openapi-validator package addresses this issue by validating requests and responses based on a provided OpenAPI spec. Having our responses validated in addition to just the requests will be a good idea as that will ensure the API code always responds in the expected schema.