Add requirements for GenericSkeleton#453
Conversation
SebSparrowHawk
force-pushed
the
ssp_requirements_generic_skeleton
branch
from
6c035cd to
581ca2c
Compare
|
|
||
|
|
||
| ScoreReq.CompReq GenericSkeletonEventListSource { | ||
| description = '''A {{GenericSkeleton}} instance shall deduce its supported events from the {{LoLa}} JSON configuration containing deployment information. |
There was a problem hiding this comment.
Hm. Not sure?
The GenericSkeleton gets the list of events/fields (and at some point also methods - we haven't implemented this yet, but need to do soonish) via parameter in Create(). So the TRUTH is in this parameter of type GenericSkeletonServiceElementInfo ... the related existance of these elements (events/fields) in the mw_com_config.json is also a requirement ... but I would then have a separate req!
The separate req. says, that the GenericSkeleton::Create() shall fail, if for one of the elements in GenericSkeletonServiceElementInfo there is no correlated type/deployment info ...
| version = 1 | ||
| } | ||
|
|
||
| ScoreReq.CompReq GenericSkeletonExceptionLessCreation { |
There was a problem hiding this comment.
You are not talking about potential errors here? In OfferService you do ...
| version = 1 | ||
| } | ||
|
|
||
| ScoreReq.CompReq GenericSkeletonGetEvents { |
There was a problem hiding this comment.
You could already create/duplicate these reqs. for fields! Even if it is currently not implemented ... but should be done soonish and then we already have the reqs.
|
|
||
| } | ||
|
|
||
| section "Generic_Skeleton_Event" { |
There was a problem hiding this comment.
You can "copy" this section for Fields - do a simple 1:1 copy - which means, that right now we would not have get/set functionality for the GenericField ... this we will add later on req. level, when we now, how we want to deal with methods at all.
| } | ||
| } | ||
|
|
||
| ScoreReq.CompReq DataTypeMetaInfo { |
There was a problem hiding this comment.
please double-check with Brendan! Afaik we also have/use {{score::memory::DataTypeSizeInfo}}, which is almost identically! Maybe we have to refactor/clean-up code
2 participants
No description provided.