[14.0][ADD] endpoint_product_catalog - #1645
Conversation
49a900f to
0f7b4fe
Compare
| # See https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst#oca_dependencies-txt | ||
| reporting-engine | ||
| server-ux | ||
| web-api |
There was a problem hiding this comment.
no need to touch this file but... yeah... maybe somebody is still using it.
Although I'm not sure this is the right place for this module (the repo I mean). Maybe "PIM" is more appropriate even if not directly bound.
There was a problem hiding this comment.
Should I move it to the PIM repo?
There was a problem hiding this comment.
I don't really have an opinion, as I don't see the immediate benefit of such a module. In my mind, exposing an API means exposing a contract and the system must at all times ensure that the data is validated against the contract while being able to provide documentation detailing the terms of the contract.
Apart from this comment, the web-api repo would probably be more appropriate, or a new web-api-contrib repo.
There was a problem hiding this comment.
Validation and documentation will come. ATM is not fundamental and we need some freedom here 😉
There was a problem hiding this comment.
I'm proposing the new repo here OCA/repo-maintainer-conf#27
|
moved to OCA/web-api-contrib#1 |
Allows configuring specific endpoints to expose products catalogs.