-
Notifications
You must be signed in to change notification settings - Fork 7
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
no-issue: Split DataBroker pullMetadata API per type #5288
Conversation
['delete', [{ code: 'DHIS_01', type: 'dataElement' }, { value: 2 }, TO_OPTIONS]], | ||
['pullMetadata', [{ code: 'DHIS_01', type: 'dataElement' }, TO_OPTIONS]], | ||
]; | ||
it('passes mapping to service: push', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section is just breaking apart the parameterised tests into separate test blocks per API
I think parameterised tests should only be used for simple, pure functions where we want to test multiple variations for the same API, e.g. maths, date handling etc. They are probably overused in tupaia
(guilty as charged!)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All lgtm!! Thank you as always @kael89
DB_PASSWORD= | ||
DB_PORT= | ||
DB_URL= | ||
DB_USER= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding the example
Thanks for the review @edmofro, can I merge this? |
Yes go for it! |
Splitting
DataBroker.pullMetadata
into two APIs, one for data elements and one for data group.Splitting the Service APIs will be done in another PR