They check exact equality of TypeInstances, but the uses and usedBy field can contain different order of TypeInstances. That causes the integration tests to fail
Options
The options we should consider:
sort related TypeInstances in the uses and usedBy
For consistency, we should also sort TypeInstances for typeInstances resolver
Description
The TypeInstance assertions in
test/e2e/hub_test.go:341
are problematic:They check exact equality of TypeInstances, but the
uses
andusedBy
field can contain different order of TypeInstances. That causes the integration tests to failOptions
The options we should consider:
uses
andusedBy
typeInstances
resolvertypePath:revision
?@relation
directive - see docs https://github.com/grand-stack/grandstack.io/tree/20699840156454caf4f411da96bcc98cba135b95/website/docsFull error
https://github.com/capactio/capact/runs/5245477683?check_suite_focus=true