[FIX] shopfloor_base: Set _menu and _profile as properties

[rousseldenis]

As soon as work context is not loaded yet at service init(), change them to properties to allow dynamic evaluation.

[OCA-git-bot]

Hi @simahawk, @guewen, @sebalix,
some modules you are maintaining are being modified, check this out!

[simahawk]

I'm not sure to understand what you are trying to fix 🤔
What's the use case?

I think I did that on purpose to freeze the two variables at component instance level.
See acsone@9dfe2ab

[nicolas-delbovier-acsone]

I'm not sure to understand what you are trying to fix 🤔 What's the use case?

I think I did that on purpose to freeze the two variables at component instance level. See acsone@9dfe2ab

Personally, I needed this while debugging #1085. I had the same problem that described here: the variables where not populated when I called them.

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

[simahawk]

I'm not sure to understand what you are trying to fix 🤔 What's the use case?
I think I did that on purpose to freeze the two variables at component instance level. See acsone@9dfe2ab

Personally, I needed this while debugging #1085. I had the same problem that described here: the variables where not populated when I called them.

Debugging what and how? If you lookup the component using component machinery, if the work context used it's properly set before the component is initialized I see no reason to no have the value propagated.

If you had this issue only on tests and not while using the app, then you might have something wrong in the tests.
I'll check on that PR.

[rousseldenis]

I see no reason to no have the value propagated.

That's the case in production with real behavior. The values are void

But why should not menu and profiles can be evaluated at runtime ?