ComponentProxy uses LC::Check::NoAction

[stdweird]

Investigate if we should/can switch to CAF::Object::NoAction

[stdweird]

• each component class sets CAF::Object::NoAction to the noaction from this_app
  • it is not reset on destroy or anything, a single load is enough
  • anything using CAF while running noaction in ncm-ncd uses NoAction
• componentproxy sets LC::Check::NoAction (and sets it back afterwards)

propose to switch to a method to set and restore the Noaction on all possible related modules in ComponentProxy

[stdweird]

also, every component has its own NoAction variable (and it's exported).
it is sometimes used by the components.

this variable is set first and then CAF::Object::NoAction gets the same value.

this is getting confusing very fast.

[jrha]

Discussed at RAL workshop, concluded that this is not urgent, but if @stdweird feels like working on it... feel free.