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

dhis2 Document which DHIS2 adaptor versions are supported by which OpenFn adaptor versions #61

Closed
aleksa-krolls opened this issue Jul 4, 2022 · 1 comment · Fixed by #861
Assignees

Comments

@aleksa-krolls
Copy link
Member

Especially with the release of DHIS2 v2.38 (see issue #62 ), there may be pretty significant differences between DHIS2 API versions.

On this adaptor repo (and maybe also in the OpenFn app), we should make obvious which DHIS2 API versions are supported by which OpenFn adaptor versions... because some DHIS2 API versions may require a new major release of the OpenFn adaptor.

At least is it possible to document the DHIS2 API versions the current OpenFn adaptor has been implemented for/tested against?

@elias-ba elias-ba transferred this issue from OpenFn/language-dhis2 Oct 21, 2022
@elias-ba elias-ba changed the title Document which DHIS2 adaptor versions are supported by which OpenFn adaptor versions dhis2 Document which DHIS2 adaptor versions are supported by which OpenFn adaptor versions Oct 21, 2022
@taylordowns2000 taylordowns2000 moved this to Icebox in v2 Feb 3, 2024
josephjclark added a commit that referenced this issue Jun 11, 2024
@aleksa-krolls
Copy link
Member Author

@hunterachieng maybe we can update the adaptor's Overview page to say this?

@mtuchi mtuchi linked a pull request Dec 9, 2024 that will close this issue
12 tasks
@mtuchi mtuchi mentioned this issue Dec 9, 2024
12 tasks
@github-project-automation github-project-automation bot moved this from Icebox to Done in v2 Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants