-
Notifications
You must be signed in to change notification settings - Fork 1
Conversation
Hi @teug91 thank you for this PR! Are you using this version of the HeaderBar with I've been wanting to update the links and icon paths here to support 3rd party domain deployments and non-core apps for a while. I think we will want to use Context rather than prop-drilling, as you say. I'll be extending the API of dhis2/app-runtime shortly with a new hook to access application configuration (especially the I'll let @varl make the call on whether to accept this as-is and then update it to use context, or to wait for the new context accessor (probably next week). |
Yes, I'm using this version along with It makes no difference to me if we have to wait for context or if the PR is accepted. Thanks. |
It's been almost a month, so I'm going to go ahead and merge this for now, and we can refactor down the line. This doesn't touch the external component API, so refactoring to Context down the line is a non-breaking change. Thanks for this, @teug91. |
## [1.0.7](v1.0.6...v1.0.7) (2019-07-05) ### Bug Fixes * **headerbar:** links and app icons ([#20](#20)) ([2758ce6](2758ce6))
🎉 This PR is included in version 1.0.7 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@varl OK sounds good. For reference: This is the app-runtime change to enable context-provided application config dhis2/app-runtime#13 |
There is a lot of
contextPath
prop-drilling. Do you prefer another implementation? UsinguseContext
perhaps?Also, maybe the locale stuff can be moved into the
useEffect
?