OperationalContext - seperate logic from presentaion

[JoshRosenstein]

After realizing i couldn't use some components without having them wrapped in OperationalUI and then reading over useOperationalContext Feature,

Whenever you choose to refactor some of the components like (Button, Breadcrumb,Logo etc), I think it would be best to separate out the logic from UI components. I dont need to preach the reasons why, but i thought after seeing that PR, that would be a good time to do it when those get refactored.

Also you can even take it a step further and breakdown and export everything like Uber/baseui 😄

[TejasQ]

Great idea! Do you have a little bit more concrete information about which components would be touched?

[JoshRosenstein]

• Breadcrumb

• Logo

• Input.Button

• SimpleLink

• SidenavItem

• Button

• SidenavHeader

• off topic but just 👀simpleLink, and wonder if there are more components like this where you should pull the container out from under and make use of the (as-prop)[https://emotion.sh/docs/styled#as-prop]

[TejasQ]

This is a great idea! It's actually a continuation (IMO) of #911. Let's do it and HOOKS ALL THE THINGS! Wanna collab?

[JoshRosenstein]

Yeah saw that and why i brought it up as it would be a perfect time to knock out 2 birds with one stone. I gotta get used to correctly linking my refs haha.

[TejasQ]

I think this is closable since we merged #911, right, @JoshRosenstein?