feat(*): refactor Go SDK to be more intuitive #604
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a major change to the Go SDK to make building dictionaries declaratively more intuitive. A number of renames have taken place, notably:
Representable
types are now just the default types. SoDictionaryRepresentable
is now justDictionary
.Buffer
prefix. So the oldDictionary
type, which used to be a FlatBuffer, is now calledDictionaryBuffer
.AsRepresentable()
toStruct()
AsBuffer
toBuffer()
and updated it to return an actual FlatBufferTable()
method that returns what the oldAsBuffer()
method used to – a FlatBuffers table offsetBytes()
method that returns a byte arrayCompile
andWrite
methods. AnyCompile
method will accept a path/XML/dictionary/etc and give you a fully qualified ODict byte buffer back, whereasWrite
does the same thing, except it writes the buffer to the specified output path and gives you the bytes writtenThe docs site will need to be updated.