while intended for top-down usage, keeps terminology of bottom-up for consistency with the XML element names (i.e. deals with Peptides and Peptide Evidence rather than proteoforms-related terms)
constructor overloads for either a path to the mzIdentML file or a Stream (this was done with blob-triggered Azure Functions in mind, in which you're provided a Stream)
hey @mtrobey, I just merged in master and broke a bunch of stuff because nullable ref types is now turned on. Let's discuss this on Teams and develop a next course of action