RUM-10316 - properties referencing support#2793
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## feature/v3 #2793 +/- ##
==============================================
+ Coverage 67.54% 67.62% +0.08%
==============================================
Files 818 818
Lines 30747 30745 -2
Branches 5178 5179 +1
==============================================
+ Hits 20767 20789 +22
+ Misses 8578 8564 -14
+ Partials 1402 1392 -10 🚀 New features to boost your workflow:
|
|
Can you please give more details which referenced properties are needed to be supported? Indeed, Do you mean they need to be referenced from the Logs and Traces schema instead of direct declaration there? |
Yes, thats correct, see #2794 for more details. |
What does this PR do?
In order to align
osanddeviceproperties across different events we need to have single source of truth fordeviceandosobjects. CurrentJsonSchemaReadersupports referencing only if referenced object was declared indefinitionsobject.This PR adds support for referencing object declared in
properties. Note that only whole object referencing is supported because referencing by id requires name resolution, which makes referenced type a bit different every time it referenced.see /external_nested_description_properties.json for example of new syntax supported
Motivation
We need this change in order to use rum/_common_schema.json as a source for
deviceandosobjects.Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)