Contributors mailing list archives
Re: Generic rest_api modulesby
I've also seen a third implementation, by MuK, which allows you
to basically build your REST API on the fly through the UI. So
it's generic, but also customizable by consultants.
It would be really nice to have this in OCA as well, but it would be some work.
Same goes for the "connector" framework by the way - it would be great if a consultant can just build his importer, exporter, mapper, instead of requiring the programmer.
Very good remark ! The generic one you propose is a great one. I like approaches such as this one.
Now I think this serves a different purpose I guess. A generic one allows you to access basically everything you can according to your access right and always in the same way. The other approach allows you to define what is accessible or not over REST. It also allows you to write what method with which syntax you want to have. This is clearly needed in advance interface with transactional behavior (not only data fetching).
In the end, we'd like to have both probably ;)
On Thu, Jul 7, 2022 at 9:16 AM Kitti Upariphutthiphong <firstname.lastname@example.org> wrote:
I did use the OCA base_rest, it all works fine. Except we need to create new modules for new models needed, and the collective maintenance can be high.
I have found this module pretty generic to use https://github.com/yezyilomo/odoo-rest-api. (I found this the only non-paid module so far).
Just curious why OCA don't do something more generic like the above link (which does not seem to be difficult to do either). What is the pros and cons?
On Thu, Jun 16, 2022 at 9:57 PM Raphaël Valyi <email@example.com> wrote:
I have no opinion about Sebastien's proposal. But I take advantage of the thread to mention at Akretion we created this Stock 3 PL REST API module (3rd party logistics)It can fit for 3rd party logistics when you need something simpler than Shopfloor.
The project got stalled with the pandemic and I'm still a bit over-busy to take care of pushing it to the OCA, but at least you know it exists now. I was planning to submit it to stock-logistics-workflow but eventually I'll push it to this new repo if you think it fits better.
Help for this stock_3pl_api (review and tests) would be very welcome...
On Thu, Jun 16, 2022 at 7:52 AM Benoît Guillot <firstname.lastname@example.org> wrote:
Le jeu. 16 juin 2022 à 08:22, Joël Grand-Guillaume <email@example.com> a écrit :
I'm good with the proposal Sébastien
Le mer. 15 juin 2022 à 14:07, Simone Orsi <firstname.lastname@example.org> a écrit :
On Wed, Jun 15, 2022 at 1:27 PM Mignon, Laurent <email@example.com> wrote:
I would prefer to keep the 'base' modules into their own repository. The maintainers are not the same and it's easier to maintain and manage addons within a small repo than a larger one.
+1 for the new rest-api repo.
On Wed, Jun 15, 2022 at 12:46 PM Pedro M. Baeza (Tecnativa) <firstname.lastname@example.org> wrote:
Why not renaming current OCA/rest-framework to that more generic one and host there both framework and the modules that use it? Remember that the maintenance burden increases on each new repository added to OCA.
Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
Joël Grand-GuillaumeDepartment Head
New address from 1st September 2022
Route de la Chaux 4
Discover more about our new base camp office!