can we double check to make sure that this particular rule no-$ref-siblings is set to be off?
otherwise it'll conflict with the newly implemented 'x-encrypted' extension, because both 'x-encrypted' and 'description' properties will be needed to handle the separation of the encrypted/unencrypted data structures.
can we double check to make sure that this particular rule
no-$ref-siblingsis set to be off? otherwise it'll conflict with the newly implemented 'x-encrypted' extension, because both 'x-encrypted' and 'description' properties will be needed to handle the separation of the encrypted/unencrypted data structures.