D
D
I guess having same entity id would mostly help with the debugging. On the other hand, having control of the id generation have more than one purpose. It might be...
> The entity id is the actual index used to look for the entity data, so having something negative here would be... problematic :D It is highly linked to the...
Speaking of wishes :-) it would be "so great" to be able to serialize and then de-serialize the recorder content (of course with some kind of hook that does not...
> I am curious for the reason you need to constantly synchronise entities from different worlds. When I designed the `CopyTo` method, what I had in mind was to transfer...
Not sure if it helps but using generator.SchemaReferenceHandling = SchemaReferenceHandling.None; won't generate definitions.
On a remotely related topic, we've found out that using a custom generation provider as discribed per https://www.newtonsoft.com/jsonschema/help/html/CreateCustomProvider.htm, we loose some default features such as parsing Data Annotation Attribute :...
Thanks James for your help. However, about your suggestion, while we can use ContractResolver to change some setup about the schema, we still cannot set the title and description for...
this is fixed in the latest version