-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parsed schema contains nested "type" keys #86
Comments
The issue seems to occur in the |
I've found the origin of the issue. When parsing the fields of an
When this field is later JSON encoded using the
This is the origin of the nested |
Ensuring that |
When using the
encodeRecord
method on theRecordSerializer
, I encounter an issue when theschemaId
method is called on aRegistry
class to validate that the parsed schema is registered for the subject.Specifically, the issue seems to stem from subtle differences between the parsed and remote schema. For example, the following snippet is the schema as it was parsed by this package after formatting by the
prepareJsonSchemaForTransfer
function:Whereas, the following snippet is the schema returned from a
GET
request to the registry:When I make a
POST
request to the registry for the subject with the second schema (returned by aGET
request to the registry), I receive a successful response. But, when I make aPOST
request to the registry for the subject with the first schema (parsed by the package), I get the following error:Any advice on the issue and how I can proceed is greatly appreciated. Cheers!
The text was updated successfully, but these errors were encountered: