Add PRIDE validation package

[omaus]

This PR

• adds PRIDE validation package
• closes [Feature] Add validation/QC-package for PRIDE #2

[kMutagene]

@omaus

Nice progress so far. I think my review comments on nfdi4plants/arc-validate#88 should be addressed before publishing (meanining: setting Publish true in the header).

Small request: could you add more metadata to the header? I know these are optional but especially tags would be nice. After that we can merge this so that it is accessible for the github api-based package installation already, and move to production once the helpers are refactored.

[kMutagene]

@omaus note that publishing and merging into this repo are two separate things.

We can absolutely merge this when more metadata is added.

[kMutagene]

@omaus sorry to nudge you so much but can you please add author and tag metadata so we can merge this? Should not take long.

[omaus]

@omaus sorry to nudge you so much but can you please add author and tag metadata so we can merge this? Should not take long.

Yeah thx, pls check if it is done right (I'm esp. unsure about the publish: true). 👍🏻

[kMutagene]

Lgtm, but pls do not set publish - this is intended for full immutable release, and iirc we want to adapt arcexpect api before that

[kMutagene]

But commiting to this repo makes the package available as prerease already

[omaus]

Lgtm, but pls do not set publish - this is intended for full immutable release, and iirc we want to adapt arcexpect api before that

Done.

[kMutagene]

thanks @omaus, heads up that i will push some changes to your branch to test some ci capabilities

[kMutagene]

allright, testing pipeline seems to work and also caught multiple problems (see pipeline output).

Please make sure that the version in the yaml metadata is the same as indicated in the file name, and make sure that the script can run. Compilation of the script in ci fails, and i suspect that that is due to the versions of the nuget packages not being pinned, and ARCExpect API having changed since you submitted the PR.

I will add a test that checks that all nuget references are pinned.

[omaus]

@kMutagene

Unit test says that version is wrong. I don't see why that should be the case. The file's name is "pride@1.0.0.fsx", YAML tags:

MajorVersion: 1
MinorVersion: 0
PatchVersion: 0

???

[kMutagene]

???

Those are the default values the metadata class gets initialized with if the frontmatter is invalid !!!
Note that also the StagingDirectory.FileContent.All files have valid metadata test fails. The issue is that your file gets checked out with LF on windows instead of CRLF. Not sure why but i really do not care, ill just replace line endings on parsing frontmatter.

[kMutagene]

Also, name in ontology tags should be Name, which is my bad.