-
Notifications
You must be signed in to change notification settings - Fork 13
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
MetaInfo: creator is optional now #190
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few thoughts; I don't particularly love this spec change and I don't really like changing a spec without some kind of spec version bump but those things don't matter, but if this is the consensus then let's certainly make the change :)
@@ -77,7 +77,7 @@ fn is_zero(v: &u32) -> bool { | |||
impl Default for MetaInfo { | |||
fn default() -> Self { | |||
MetaInfo { | |||
creator: DEFAULT_METAINFO_CREATOR.to_string(), | |||
creator: Some(DEFAULT_METAINFO_CREATOR.to_string()), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe just default to None
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, and set the creator on saving? I'd prefer to keep the explicit norad reference, since norad is the only user of it currently.
@@ -64,7 +64,7 @@ pub enum FormatVersion { | |||
#[derive(Debug, Clone, Serialize, Deserialize, PartialEq)] | |||
#[serde(rename_all = "camelCase")] | |||
pub struct MetaInfo { | |||
pub creator: String, | |||
pub creator: Option<String>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is right, but in line with the other changes you've been making we could also just treat the empty string as none. (I prefer this way, though, it's more explicit and more "correct".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mh, an empty string would still land in the serialized stream unless I stop serde; and the spec doesn't say that the field must be non-empty 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good!
OK to merge? |
See unified-font-object/ufo-spec#192.