[13.0] Improvements on server.env.techname.mixin

[ivantodorovich]

ping @simahawk

What do you think about this?

Re. the mixin inherit (154090a), I guess it wasn't done like this before because one may use server.env.techname.mixin without server.env.mixing but I can't see why one would want to do that.. I find this way easier to use and in most cases saves a few line breaks

[simahawk]

Re. the mixin inherit (154090a), I guess it wasn't done like this before because one may use server.env.techname.mixin without server.env.mixing but I can't see why one would want to do that.. I find this way easier to use and in most cases saves a few line breaks

yeah, it was in my mind for a while. At first I wanted to keep it isolated but it turns out you always use them in combo.

Thanks for taking care of my TODOs! 😄

[simahawk]

@ivantodorovich could you test this on OCA/search-engine ?

[simahawk]

@ivantodorovich ping :)

[ivantodorovich]

@ivantodorovich could you test this on OCA/search-engine ?

It seems ok
Is there something specific you have in mind?

[simahawk]

just use this change there and see if you get a green build ;)

[ivantodorovich]

just use this change there and see if you get a green build ;)

Indeed it's not working.

connecto_search_engine would need to be adapted to have the index_prefix_name in a computed field.

But also I tried that, and it's not working as expected. Since server_environment "transforms" fields into computed fields to read from config. I created this issue to explain it: #85

I couldn't find a simple solution for now :/ so best if we close this and reevaluate in a future migration IMO

[simahawk]

@ivantodorovich you can reconsider this here #122 😉