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

fix(organisation-unit-tree): change behaviour of renderNodeLabel so that return value is label contents instead of label component #696

Merged
merged 1 commit into from
Aug 10, 2021

Conversation

mediremi
Copy link
Contributor

This PR is a cherry pick of changes made in #681 regarding the renderNodeLabel prop of the organisation unit tree.

…hat return value is label contents instead of label component
@cypress
Copy link

cypress bot commented Aug 10, 2021



Test summary

512 0 0 0


Run details

Project ui
Status Passed
Commit 7bd2cc3
Started Aug 10, 2021 1:49 PM
Ended Aug 10, 2021 2:03 PM
Duration 13:36 💡
OS Linux Ubuntu - 20.04
Browser Electron 89

View run in Cypress Dashboard ➡️


This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

@mediremi mediremi merged commit c2ce614 into master Aug 10, 2021
@mediremi mediremi deleted the fix/org-unit-render-node-label-changes branch August 10, 2021 14:25
dhis2-bot added a commit that referenced this pull request Aug 10, 2021
## [6.15.1](v6.15.0...v6.15.1) (2021-08-10)

### Bug Fixes

* **organisation-unit-tree:** change behaviour of renderNodeLabel so that return value is label contents instead of label component ([#696](#696)) ([c2ce614](c2ce614))
@dhis2-bot
Copy link
Contributor

🎉 This PR is included in version 6.15.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@varl varl mentioned this pull request Sep 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants