Pavel Bodiachevskii

@jonaslagoni not sure, but looks like similar problem after update to 49 log ``` [Error] TypeError: e.dependencies is not a function. (In 'e.dependencies()', 'e.dependencies' is undefined) — resources:32:1883716 ia (resources:32:539997)...

> Should be fixed with the recent version, can you check if it still occurs? Renders as expected test specs. I checked rendering on `[email protected]/` and `[email protected]/` Is it ok,...

@dalelane @smoya @char0n @GreenRover

> Regarding point 1, I see the regex we show in [our documentation](https://www.asyncapi.com/docs/reference/specification/v3.0.0#specificationExtensions) doesn't correspond with the one enforced in our [JSON Schema documents](https://github.com/asyncapi/spec-json-schemas/blob/master/schemas/3.0.0.json#L4700-L4704), which indeed allows for . characters....

> Regarding point 1, I see the regex we show in [our documentation](https://www.asyncapi.com/docs/reference/specification/v3.0.0#specificationExtensions) doesn't correspond with the one enforced in our [JSON Schema documents](https://github.com/asyncapi/spec-json-schemas/blob/master/schemas/3.0.0.json#L4700-L4704), which indeed allows for `.` characters....

I understood root of this problems. Here is fresh example - https://github.com/asyncapi/jasyncapi/issues/160 > Might make sense to maybe finally formalize it in the spec and [add to the list in...

> > Might make sense to maybe finally formalize it in the spec and [add to the list in here](https://github.com/asyncapi/spec/blob/master/spec/asyncapi.md#fixed-fields-24). Not sure 🤔 > > Even though we could see...

> > so we must clarify this situation and decide what to do with properties from OAS schema > > > > I think we are clear "enough" about that...

> Strange but after adding #1034 the adeo example fails validation. We definitely need to push #957 for next bounty: > > ``` > Diagnostic err: "0" property type must...

@derberg @jonaslagoni can I close issue?