Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reporting/overview system for collection/process metadata merging issues #76

Closed
soxofaan opened this issue Sep 27, 2022 · 5 comments
Closed

Comments

@soxofaan
Copy link
Member

follow up of #4 (merging of process metadata) and #5 (merging of collection metadata):

It turns out that there can be quite some issues when merging metadata, of varying degrees of importance/impact.
It would be good if we have some kind of system to get an overview or report issues

@soxofaan
Copy link
Member Author

soxofaan commented Sep 27, 2022

still needs a bit of brainstorm to make more concrete, but some things to consider:

  • allow this to run as kind of integration tests (e.g. critical merge issues have to be resolved before deploying)
  • allow to run continuously as cron and report (e.g. daily health check)
  • allow other parties/back-ends to run this against a dev build for example
  • keep it simple as cli tool (which reporting format then?), or make it a web view (with auth?)

JeroenVerstraelen added a commit that referenced this issue Oct 10, 2022
JeroenVerstraelen added a commit that referenced this issue Oct 10, 2022
@JeroenVerstraelen JeroenVerstraelen linked a pull request Oct 10, 2022 that will close this issue
JeroenVerstraelen added a commit that referenced this issue Oct 12, 2022
JeroenVerstraelen added a commit that referenced this issue Oct 12, 2022
JeroenVerstraelen added a commit that referenced this issue Oct 14, 2022
@soxofaan
Copy link
Member Author

#77 has been merged now

@soxofaan
Copy link
Member Author

soxofaan commented Nov 10, 2022

With #77 being merged the big chunk of work is done. Some additional minor follow-up TODOs:

  • process metadata merging:
    • merge "deprecated"
    • merge "experimental"
    • merge "examples"
    • merge "links"
    • ignore "description" when comparing "returns" field
    • report missing parameter "description" (which is required) instead of falling back on "name"
  • collection metadata merging: check TODO comments in code
  • general
    • MarkDownReporter: drop distinction between warning/critical, or handle it more generically
    • define common interface for reporter classes (instead of disconnected MarkDownReporter and LoggerReporter
    • validator.py: add cli option to select check for collections only, processes only or both

@soxofaan
Copy link
Member Author

@soxofaan
Copy link
Member Author

most follow up TODO's are done or moved to separate tickets.
I think we can close this #76 now.

thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants