-
Notifications
You must be signed in to change notification settings - Fork 25
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
SteppingGranularity is not a struct but a string alias and should not use a pointer #80
Comments
Not all type aliases seem to be affected: Affected types:
Not affected:
The tricky part is that we process stuff in the order it is in the JSON file, so by the time a property of type One possibility would be to hard code the known type aliases somewhere - that does not feel ideal, but we are doing it already for cases where the spec defines an omitted optional boolean to be interpreted as true, and we used to also do this for structs. The other option is to make a second pass to collect these before starting to emit in source order. It looks like we are anyways not streaming anything, and unmarshal all definitions before starting with any emitting here: go-dap/cmd/gentypes/gentypes.go Line 595 in d1322a7
|
I think I found a bug in my own PR that is now released as v0.9.0:
go-dap/schematypes.go
Line 914 in d1322a7
But this is not actually a struct, so it does not need to be a pointer to be omitted from JSON:
go-dap/schematypes.go
Line 1880 in d1322a7
I will look into a fix tomorrow.
The text was updated successfully, but these errors were encountered: