v2.0.0

The TypeScript rewrite of Odoo Debug, for Odoo 18.0, 19.0 and 20.0: every difference between them in one adapter per
version, checked against the database on each page.

• Record: every field of the record (definition, value by type, what recomputes it), quick filters, copy as JSON.
• View: the view told as a story: which views from which modules build it, in Odoo's order; one field through them; the combined arch.
• RPC: the page's JSON-RPC calls; a call opens as its request, edited and sent again right there (the recorded answer below it until then); a new request; Copy as cURL for the external API (18: /jsonrpc, 19: /json/2); ⏱ Profile a call (Perf).
• Security: rights as tables (ACLs and rules × operations, domains evaluated for the user); rights on every model; groups, what each grants, who has it; try a group; compare users.
• Translations: where a text comes from and where to change it; a record's and a view's translations; .po coverage, export, import; languages.
• Apps: modules as in Odoo's Apps menu; Activate / Upgrade / Open Forms; ⚠ code newer than the database; a module's description, manifest, dependencies both ways (what an install brings, auto-install included, as Odoo computes it) and as a diagram, its data and models; uninstall previewed by Odoo's wizard; operations left pending.
• Menus: the technical screens a developer opens all day (Models, Fields, Record Rules, Views, Crons, Actions, Parameters…), one click away without debug mode; opened in the Odoo page, ↗ in a new tab.
• Perf: Odoo's profiler read back, the requests slowest first (static files apart): each request's diagnosis (what to look at first: an N+1 and the line running it, the database, Python, or nothing), its time split SQL / Python and by function of the modules (from the Python samples), its SQL in words ("Reads res_partner"), code as code (function() module/path.py:line, copied on click); the lines of code sending it, N+1 suspects, the slowest queries; a baseline to compare with; flame graph; clean up.
• Code: an ORM console as the logged-in user on the screen's record / records / model: JavaScript in the page (read-only, dry run, writes) or Python on the server (a dry run rolled back for real); results shown by type; snippets.
• ⌥/Alt + click on the Odoo page copies a field's technical name: a field, its label (a readonly one too), a list cell or column header, or a tracked change in the chatter (Draft → Sent (Status): state).

Odoo 20.0: an adapter of its own, every server call, route and webclient internal the panel uses checked against the 20.0 sources (not yet run against a live 20 database).

• Security: 20's ir.access (permissions OR-ed, restrictions AND-ed) read as ACLs and record rules: the same tables and simulation; no permission refuses, every _inherits parent checked, time back in domains, the new 'access' operator flagged as uncertain when simulating another user; an AccessError saying 'delete' read as unlink.
• Apps: the uninstall preview on 20 (no show_all, applications listed apart); the modules left waiting run along with the next operation again, said per version.
• Perf: profiling allowed or not read with get_str; sessions counted with formatted_read_group.
• Translations: .po export with 20's binary read format.
• Record: binaries shown as their size on 20 (no bin_size: read with load='web').
• Code: JavaScript read_group on 20 calls formatted_read_group; exists() works (it is private on the server: checked with a search).
• RPC: Copy as cURL for /json/2 knows 20's read_group, web_unlink, no exists.
• Menus: Access Rights (ir.access) on 20, where Record Rules is gone.