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

Clarify whether or not the metadata section should exist #29

Closed
io7m opened this Issue Jan 10, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@io7m
Owner

io7m commented Jan 10, 2017

Right now, the text serializer writes an empty metadata section if no metadata exists. The parser then rejects the serialized file because "no metadata was expected".

@io7m io7m self-assigned this Jan 10, 2017

@io7m io7m added this to the 0.6.0 milestone Jan 10, 2017

@io7m io7m closed this in e0b8f21 Jan 10, 2017

io7m added a commit that referenced this issue Jan 10, 2017

Merge branch 'release/0.6.0'
Release: io7m-smfj 0.6.0
Code fix: Reduce severity of line parser log messages. (tickets: #31)
Code fix: Zero pad schema ID values. (tickets: #30)
Code change: Allow redundant use of the metadata command. (tickets: #29)
Code change: Add context values to the filter interface. This is an API breaking change.
Code change: Integrate immutables-javaslang. This is an API breaking change. (tickets: #17)

io7m added a commit that referenced this issue Jan 10, 2017

Merge tag 'io7m-smf-0.6.0' into develop
Release: io7m-smfj 0.6.0

Code fix: Reduce severity of line parser log messages. (tickets: #31)
Code fix: Zero pad schema ID values. (tickets: #30)
Code change: Allow redundant use of the metadata command. (tickets: #29)
Code change: Add context values to the filter interface. This is an API breaking change.
Code change: Integrate immutables-javaslang. This is an API breaking change. (tickets: #17)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment