ooor
ooor copied to clipboard
akretion
Odoo Ruby JSON client. Emulates ActiveRecord enough (as much as Mongoid; Implements ActiveModel) to make Rails development with an Odoo datastore straightforward
Now that we have Odoo proxies linked to Odoo sessions, the constant prefix feature sounds useless. Removing it may simplify a bit the code.
on v9 + demo data, somethig like ProductProduct.find(15).seller_ids breaks with the following stack trace: ``` D, [2016-08-29T20:45:27.435859 #1325] DEBUG -- : registering ProductSupplierinfo D, [2016-08-29T20:45:27.436148 #1325] DEBUG -- : OOOR...
it will become harder and harder to write tests that work on the demo data of all series so split them
dates are not casted for instance when doing ProductProduct.find :first this explains at least some test failures sinc the json/rpc layer is used.
often Odoo gives us domains as string (in views for instance). But we may need to send them back in json to Odoo. This would help to translate forms better...
copy this syntax https://blog.starkandwayne.com/2014/05/10/using-a-postgres-uri-with-psql/ postgres://USERNAME:[email protected]:5432/jszlmeae if not pwd in uri, then ask (else admin) use a URI parsing tool? add options: -s (secure without port) -e "some ruby expression" ->...
see http://simonecarletti.com/blog/2009/09/inside-ruby-on-rails-extract_options-from-arrays/
m2o product1.categ_id should 1st load ProductCategory proxy with just the name (default to the rec_name read) and the id. And it should hit the server and request all other lazy...
see lib/active_record/associations.rb it seems they use @association_cache the same way we use @loaded_associations in Ooor
localize URL using klass.model_name.i18n_key see human method in active_model/human.rb for instance, seems that action_view/helpers/form_helper.rb is calling it in default_submit_value via object.class.model_name.huma could be better than the current adhoc system I...