apiDoc VS accesscontrol

Compared to the first three tools, apiDoc takes a different approach towards generating documentation. Rather than rely on an API definition file like OAS, apiDoc is a package that allows you to add documentation directly into your source code through annotations. While there are third-party libraries that can create OAS files based on code annotations, having this built-in makes apiDoc slightly better if you want to control documentation through code instead of having a separate tool.

You can find it here : https://apidocjs.com/

API Link - apiDOC

apidoc is a node plugin that can be installed in the node application. This plugin helps to write and generate REST API documents for node.js applications.

This one works well: https://github.com/apidoc/apidoc

You can mitigate the pain by using libraries like accesscontrol, express-rbac, django-guardian, etc., to manage authorization more declaratively. But making sure nothing leaks is still a significant challenge.

2- https://www.npmjs.com/package/accesscontrol https://github.com/onury/accesscontrol

I used nestjsx-crud in the api we prepared. This library makes CRUD operations very easy. However, there is no support on the authorization side. That's why I made use of the accesscontrol library, which can be easily integrated with both nestjs and refine.

Access-Control

not a big fan of DSL(s), I think it adds complexity to the code, checkout this library accesscontrol all the configuration is javascript objects and more maintainable I think.

I am going through the docs accesscontrol npm library and came across code to limit the user to only readOwn resources.

what do you think about this library accesscontrol. It seems easier to grasp with its fluent syntax and no custom DSL