perrygreenfield
perrygreenfield
Extract the title (if it exists) for any attributes from the corresponding schema for that attribute and display that as part of the info() output.
You are getting this notification since you have either opened an asdf issue or contributed code to asdf. Changes are being considered to the asdf standard (for V2.0) and an...
This is an experimental feature that sought to make serialization of subclasses more convenient by reusing the superclass's schema, with some additional metadata appended to inform the library of which...
The ASDF Standard doesn't specify behavior around null values, but the Python library currently strips out any object key whose value is null. Some users would prefer that keys with...
The YAML 1.1 spec permits object keys to themselves be objects or arrays, which isn't well supported by Python (since dicts and lists are not hashable). A more serious issue...
There is a larger discussion of this on the [wiki](https://github.com/asdf-format/asdf-standard/wiki/2.0.0-roadmap), but the main reasons are to: - Make the basic standard more stable since more and more transforms are being...
There's been discussion around supporting additional compression modes offered by the blosc library, particularly zstd with blosc's byte transposition filter. Supporting the transposition would require new field(s) in the ASDF...
Some of these may represent early ideas that did not turn out to be useful. ### core/asdf * We can probably drop support for the old history format. ### core/column...
@nden pointed out that a schema that anyOf-combines number and quantity would be useful, since this is a common case, particularly in the transform schemas. ``` anyOf: - $ref: "../unit/quantity-1.1.0"...
The current draft-01 yaml-schema metaschema includes three properties related to the style of the serialized YAML: propertyOrder – specify the order in which object properties should be written flowStyle –...