Nishant Arora

We have not @eirslett, is that in the pitfalls/faqs which we missed?

Ok, thanks @eirslett will give this a shot, really appreciate your quick turnaround.

@alonpi we are using `schemaReferences` as of today based on my fork. I am not sure how to get this PR reviewed, they don't a have a contribution doc, nor...

@Nevon Schema References were added in v5.5 of Confluent Platform: https://docs.confluent.io/platform/current/schema-registry/serdes-develop/index.html#referenced-schemas So essentially any newer implementation should support this. This was a blocker for our (AppDirect) kafka deployment, and this...

@tejans24 this is ready to merge if @Nevon agrees. I can work on the protobuf/JSON ask in a seperate pr. We published an internal version using my fork and seems...

@300LiterPropofol that will not work because you need to build the module first, This project uses Azure to build the module. Internally we added a manual build step in our...

@300LiterPropofol - Clone the fork. - Install Deps: `yarn install` - Build: `yarn build` - Use it in your project like: `npm i -S ../path/to/fork`

@300LiterPropofol There shouldn't be a limit on the depth of the schema, glad the naming worked out for you. We can fix the naming, but I am not sure if...

@WhereIsMyRum [this](https://github.com/whizzzkid/confluent-schema-registry/tree/feature/schema-references) was working as is in production without any failures. Then I switched jobs, had some personal commitments and got covid, I hope it's still working there. I'll see...

@ajayyy would you be open to the idea of: - Moving to `graphql`: it's strongly typed, so all the requests are type-checked before reaching the business logic. Removing the need...