Extensions for async api? #35

Hi,

I have a question regarding AsyncAPI extension support.

AsyncAPI allows custom extensions (x-*) throughout the specification, and I'm interested in using them to model additional protocol-specific metadata (potentially for a reusable SignalR binding in the future).

Does AsyncAPI.NET currently support:

Deserializing unknown x-* properties?
Exposing them through the object model?
Preserving them when serializing the document back to YAML/JSON?

For example, if a document contains:

channels:
notifications:
x-signalr:
hub: NotificationHub

would this information be available after parsing and survive a round-trip through the library?

If not, is extension support something that is planned, or would a custom implementation be required?

Thanks!