In a jackson-js model created with 2.0, several elements are missing IndexFileAnchor. Here's the manual query I used to find them:
FQCollectScriptQuery script:
[ :e | ((e respondsTo: #sourceAnchor)
and: (e sourceAnchor isNil))
ifTrue: [ e ]
ifFalse: [ ] ]
For example, ArrayEx appears 4 times as ParametricClass, and 2 of them don't have IndexFileAnchor. The 2 that do have it appear to be conretizations, since they have 1 concreteParameters of number.
The ParametricClasses that don't have the source anchor are the generic ones, with T:
For ParameterTypes that don't have source anchors, it appears to be when they're used as concrete parameters, e.g., Array<Animal> is a concrete parameter in concrete calls to stringify<T> and parse<T> (however, I don't believe these are concrete entities, as shown in the model).
The 26 parametric methods without source anchors appear to be related to the cases of Array<Animal> above.
All of these cases can surely have tests that are inspired from the jackson-js examples.
In a jackson-js model created with 2.0, several elements are missing IndexFileAnchor. Here's the manual query I used to find them:
For example,
ArrayExappears 4 times as ParametricClass, and 2 of them don't have IndexFileAnchor. The 2 that do have it appear to be conretizations, since they have 1concreteParametersofnumber.The ParametricClasses that don't have the source anchor are the generic ones, with
T:For
ParameterTypesthat don't have source anchors, it appears to be when they're used as concrete parameters, e.g.,Array<Animal>is a concrete parameter in concrete calls tostringify<T>andparse<T>(however, I don't believe these are concrete entities, as shown in the model).The 26 parametric methods without source anchors appear to be related to the cases of
Array<Animal>above.All of these cases can surely have tests that are inspired from the
jackson-jsexamples.