It would be great to have support for defining fields that live inside the context object of an event payload, such as those required by Segment’s Consent Preference Updated event.

These fields are not part of the top-level event properties but are instead nested within the context object. Currently, Avo does not provide a clear way to document or manage this kind of structure.

This functionality would help teams properly define and validate events like consent events that follow Segment's standard, and more generally improve schema support for nested field requirements.