You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In whatwg/meta#23, Domenic wants to be able to include the bare minimum of metadata information in his specs, and have the rest of it (which is generally boilerplate, and inferrable from the shortname) auto-generate.
I think the best way to go about this is to have a Python hook that runs after all metadata is processed, before metadata validation, that lets you fill in additional metadata. I don't think anything less powerful will work; in particular, string substitution probably isn't sufficient.
The text was updated successfully, but these errors were encountered:
Yeah, it looks like I should probably do a dumb string substitution first, because it's easy, and then perhaps do a Python thing after for more complicated use-cases.
Ok, just pushed this fix. Went with a simple solution for now - there's a new computed-metadata.include boilerplate file you can use, which will get macro-substituted before being evaluated and added to the document's metadata. Otherwise it's identical to defaults.include.
Note that, by necessity, this overrides any metadata set by any other source, so make sure that everything you put in that file is what you definitely want in every spec for your Group.
In whatwg/meta#23, Domenic wants to be able to include the bare minimum of metadata information in his specs, and have the rest of it (which is generally boilerplate, and inferrable from the shortname) auto-generate.
I think the best way to go about this is to have a Python hook that runs after all metadata is processed, before metadata validation, that lets you fill in additional metadata. I don't think anything less powerful will work; in particular, string substitution probably isn't sufficient.
The text was updated successfully, but these errors were encountered: