Skip to content
This repository has been archived by the owner on Jul 18, 2024. It is now read-only.

Use a shared header component, instead of a custom one. #70

Closed
Tracked by #71 ...
Carlos-Muniz opened this issue Mar 22, 2022 · 3 comments · Fixed by #74
Closed
Tracked by #71 ...

Use a shared header component, instead of a custom one. #70

Carlos-Muniz opened this issue Mar 22, 2022 · 3 comments · Fixed by #74
Assignees

Comments

@Carlos-Muniz
Copy link
Contributor

Carlos-Muniz commented Mar 22, 2022

Pick up where #36 left off and refactor the frontend-app-library-authoring header to use frontend-component-header in such a way that is also usable by frontend-app-course-authoring (currently the only other Studio-like MFE).

@Carlos-Muniz Carlos-Muniz self-assigned this Mar 22, 2022
@Carlos-Muniz Carlos-Muniz removed their assignment May 26, 2022
@arbrandes arbrandes changed the title To use the shared header component, instead of a custom one. (Basically rebasing, reviewing, and merging this.) Use a shared header component, instead of a custom one. Sep 30, 2022
@arbrandes arbrandes transferred this issue from openedx/wg-frontend Sep 30, 2022
@arbrandes
Copy link
Contributor

@brian-smith-tcril, can you please assign yourself?

@arbrandes arbrandes moved this from In progress to In review in Frontend Working Group Sep 30, 2022
@brian-smith-tcril
Copy link
Contributor

@arbrandes looks like i don't have perms to assign myself

@arbrandes
Copy link
Contributor

Hmm, but now that you commented, I was able to assign it to you. (GH project woes. 🙄)

Repository owner moved this from In review to In progress in Frontend Working Group Oct 21, 2022
@arbrandes arbrandes moved this from In progress to Closed in Frontend Working Group Nov 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.