Skip to content
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

Add optional root table to SetString and ResizeVector, when your Flatbuffer isn't the schema's root type. #237

Merged
3 commits merged into from
Jul 22, 2015

Conversation

jonsimantov
Copy link
Contributor

This allows you to use these functions with a flatbuffer whose root
table type does't correspond with the root table type of the schema.

If you don't specify the table name, it will use the root table from
the schema by default (mimicing the current behavior).

This allows you to use these functions with a flatbuffer whose root
table type does't correspond with the root table type of the schema.

If you don't specify the table name, it will use the root table from
the schema by default (mimicing the current behavior).
Was previously using table name, but no reason not to just let the
calling code worry about getting the object.
@jonsimantov jonsimantov changed the title Add optional root table name to SetString and ResizeVector. Add optional root table to SetString and ResizeVector, when your Flatbuffer isn't the schema's root type. Jul 22, 2015
ghost pushed a commit that referenced this pull request Jul 22, 2015
Add optional root table to SetString and ResizeVector, when your Flatbuffer isn't the schema's root type.
@ghost ghost merged commit 62af533 into google:master Jul 22, 2015
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant