Skip to content

Add non-redundant header entries as a list of name-value tuples #29

@jeromekelleher

Description

@jeromekelleher

Rather than storing the entire header as a single string attribute, we should store all non-redundant header entries as a list of name,value tuples.

Non redundant here means not storing CONTIG, INFO, FILTER and FORMAT header entries as these are already fully encoded elsewhere.

We store the header metadata as a list of (name, value) tuples because there is no requirement that keys are unique. Header information SHOULD be stored in the same order that the items appear in the original header.

I think this is sufficient for lossless round-tripping.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions