Skip to content

API versioning #3

Open
Open
@ryanc-me

Description

@ryanc-me

Right now, we aren't considering the Odoo version at all.

Because of that:

  1. We can't use the type system to guarantee that a particular API method is available.
  2. We can't have multiple versions of an API endpoint (e.g., if Odoo changed the call_kw method slightly)

I'm not actually sure this would be a desirable feature. A few downsides would be:

  1. Much more rigid - users would need to store a version-typed Client object, or else use match {} blocks to cover all possible Odoo versions
  2. More difficult to maintain
  3. How would we handle SaaS versions (like 16.3 and 16.4 which are actually closer to 16.0 and 17.0 respectively)

It does seem like the Odoo APIs are very stable (perhaps because they're used internally), so maybe this is all fine.

One option might be some runtime-checks - that would eliminate issues 1 & 3 above.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions