fix: add html push analytics

[ghost]

https://dhis2.atlassian.net/browse/DHIS2-16929

Todo

• Add custom components for html push analytics parameters:
  • dashboard, map of label to id from /api/dashboards, singleselect
  • receivers, map of label to id from /api/userGroups, singleselect
  • mode, set of labels, to be retrieved from the constants prop of the parameter, singleselect
• Update tests

Follow up

• Check where we have hardcoded components that could be handled by dynamic components (seems like we have three potential types of complex inputs, singleselect, multiselect and transfer and two types of dynamic data, maps or sets) (https://dhis2.atlassian.net/browse/DHIS2-15336)
• Check where the backend response doesn't conform to FE expectations (this is where we might have unnecessary hardcoded components) (https://dhis2.atlassian.net/browse/DHIS2-15336)
• Or, instead of the two above just refactor the app to use a proper declarative structure as planned, which would resolve them both (https://dhis2.atlassian.net/browse/DHIS2-15336)
• Check if and where we're skipping job types or parameters (these indicate untranslated job types or unhandled parameter field types) (https://dhis2.atlassian.net/browse/DHIS2-15336)
• Proptype errors (https://dhis2.atlassian.net/browse/DHIS2-17022)
  • lastExecuted can't be required because it isn't always present
  • Invalid prop input.value of type string supplied to QueueTransfer, expected array, when there are no jobs for the queue

[dhis2-bot]

🚀 Deployed on https://pr-598--dhis2-scheduler.netlify.app

[kabaros]

tested this and it looks fine - the job itself fails, but I guess that has nothing to do with scheduler itself.

[ghost]

tested this and it looks fine - the job itself fails, but I guess that has nothing to do with scheduler itself.

I assume not. The scheduler's responsibility basically ends with the POST of the (new or edited) job details to the backend. But it might be worth mentioning it to Jan Bernitt.

[ghost]

Let me know what you think of my feedback @kabaros. If you're ok with it this PR is good to go imo.

[kabaros]

Let me know what you think of my feedback @kabaros. If you're ok with it this PR is good to go imo.

yeah it makes sense, I don't think it's in the scope of this PR to check the job itself - I am ok for the PR to be merged.

[dhis2-bot]

🎉 This PR is included in version 101.5.0 🎉

The release is available on:

• AppHub release
• GitHub release

Your semantic-release bot 📦🚀