-
Notifications
You must be signed in to change notification settings - Fork 1
Reusable HURUMap Components #1036
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
Conversation
@kelvinkipruto We could break this PR to smaller PRs. I think it is really important in migrating PesaYetu. |
@CodeForAfrica/tech |
Can we get this reviewed & merged today @CodeForAfrica/tech ? |
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.
🚀
@kelvinkipruto , I have one question regarding the migration.... if a reusable HURUmap component is importing something from @commons-ui/next
does that necessarily mean that it should be in @hurumap-next
?
Besides the question from @m453h, is there anything holding this PR back @kelvinkipruto ? |
@kilemensi Nothing else holding it back. |
@kelvinkipruto to add a bit more context on this....I had seen there are a couple of components in
In my mind I had thought they should automatically be in |
I'm probably missing something but these are the components in @hurumap-core package @m453h :
|
... or are those the new components @kelvinkipruto is trying to move into @hurumap-core @m453h ? |
@m453h |
If it's missing, lets update the packages' respective READMEs @kelvinkipruto / @m453h :
|
Hold on
@kilemensi I was referring to the new components that are added/moved to @hurumap-core in this PR I believe the list you shared is on the main branch. This is the full list
|
Then I guess over to @kelvinkipruto ... I believe my previous message should clear where each component should be going. |
Signed-off-by: Kipruto <[email protected]>
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.
👍🏽
Looks like you still need to review what goes into which package.
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.
Haven't run it locally but code LGTM 🚀
Create an issue to move all payload
related code in the current @hurumap/next
package into a new @hurumap/payload
package (similar to @commons-ui/payload
)
Tracked in #1067 |
Description
This PR makes HURUMap components reusable across multiple apps. This is done so as to reuse them for PesaYetu.
PS: This PR however does not move components that import assets/svg.
Type of change
Screenshots
Checklist: