Bump aidbox-ts-sdk: fix extension on nested elements - #124
Conversation
|
This bump targets sdk The #8121 fix has been re-applied onto |
Bumps aidbox-ts-sdk 484b967 -> 6a29dc0 (development tip), picking up aidbox-ts-sdk#151: fhir-autocomplete resolveElements now includes id/extension/modifierExtension for nested backbone/complex elements, fixing the editor falsely flagging a valid `extension` on e.g. QuestionnaireResponse.item / Patient.contact and omitting it from autocomplete. Fixes HealthSamurai/sansara#8121 Co-Authored-By: Aleksandr Kislitsyn <aleksandr.kislitsyn@gmail.com> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1bf3dd7 to
74078a0
Compare
|
Re-pointed: now bumps aidbox-ts-sdk |
Bumps the
aidbox-ts-sdksubmodule484b967 → bf86fae(current sdk master) to pick up aidbox-ts-sdk#150.What it fixes
The FHIR editor falsely flagged a valid
extensionon nested elements as anUnknown property, and omitted it from autocomplete — e.g.QuestionnaireResponse.item[].extension,Patient.contact[].extension. #150 fixesresolveElementsto include the universal element properties (id/extension, plusmodifierExtensionon BackboneElements/resources) that a StructureDefinition differential doesn't repeat for nested elements.Fixes HealthSamurai/sansara#8121.
Note on the pointer change
The previous pin
484b967("indent with two spaces") was an sdk commit that was never merged to sdk master — it targeted the oldindentUnit/insertTabTab-handling code, which sdk master has since replaced withcomputeYamlNewlineIndent. So this bump moves forward to sdk master's current indentation handling; the orphaned commit is superseded, not a live feature being dropped. (Worth a quick confirm that 2-space editor indentation still behaves as expected on master — independent of this fix.)🤖 Generated with Claude Code