First version of new API for Launch Manager - #377
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
|
It looks like it could work. To see if this if this is the right fit in combination with |
I like this suggestion. Would it be possible to add a dummy details/lm_controlimpl.hpp with a test that just shows how the API interaction would look like from the users perspective? |
pawelrutkaq
left a comment
There was a problem hiding this comment.
I would fix most of descriptions as they are bloated
|
|
||
| /// @brief Factory method — create a connected ILmControl instance. | ||
| /// | ||
| /// Establishes the mw::com connection to the Launch Manager. |
There was a problem hiding this comment.
I'd say interface shall be silent about internals (in this case mw::com)
There was a problem hiding this comment.
I'm not sure how we can avoid that...
The instance_specifier param has to be the mw::com instance specifier and additionally, there is also requirement that mw::com has to be initialized by the user, before this method is called.
Do you have a proposal in mind?
There was a problem hiding this comment.
@NicolasFussberger why do we expose mw::com instance specifier to the user ? This means we expose the service definition to the user. It feels like you can put any name here - did i miss something that mw_com in no longer internal communication channel ?
There was a problem hiding this comment.
As far as I know the instance specifier name passed here has to be defined in the mw::com config file.
So it would be either the user can pass it to the API,
or we would need to use a hardcoded name and documentation tells the user to configure exactly this name in the mw::com config file.
There was a problem hiding this comment.
I would say we need more time to experiment on how this should be configured.
We can find solution later when we have more experience with mw::com
There was a problem hiding this comment.
It has to be passed, but it shall be internal inho. This string connects to EXACT declaration of service type and its instance. So we shall provide an "mw_com_config fragment" with opur definition which user shall put into its json file until mw_com will not solve the issue of multiple configs. But exposing this to user sounds like bad idea.
There was a problem hiding this comment.
Should this interface then be marked WIP somehow that its probably going to change? or we remove this immediately, really (i prefer second option)
f8a846a
First draft of new API for Launch Manager