Skip to content

Conversation

@bfollington
Copy link
Contributor

@bfollington bfollington commented Feb 3, 2025

  • Factoring chunks out for re-use between lit and react
  • Port os-chrome to React experiment
Screen.Recording.2025-02-03.at.1.20.38.pm.mov

@bfollington bfollington requested review from anotherjesse and jakedahn and removed request for anotherjesse February 3, 2025 03:25
@bfollington bfollington marked this pull request as ready for review February 3, 2025 03:26
Comment on lines +7 to +27
interface SidebarProps {
homeRef: any;
linkedCharms: any[];
workingSpec: string;
focusedCharm: any;
handlePublish: () => void;
recipeId: string;
}

const Sidebar: React.FC<
SidebarProps & {
query: any;
onQueryChanged: (value: string) => void;
schema: any;
copyRecipeLink: () => void;
argument: any;
data: any;
onDataChanged: (value: string) => void;
onSpecChanged: (value: string) => void;
}
> = ({
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Messy and bloated, we need to work out where all this stuff comes from still


import * as osUi from "@commontools/os-ui";
import { OsChrome } from "@commontools/os-ui/src/components/os-chrome";
console.log(osUi);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have to use the variable or else it gets 'cleaned up' during build 🙃

Comment on lines +75 to +82
<WebComponent
slot="overlay"
as="os-fabgroup"
className="pin-br"
onSubmit={() => {
console.log("submitted");
}}
/>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can define interfaces and thin components for commonly used webcomponents using this same abstraction

it's a little bit automagical in terms of handling event names but... it works!

@jakedahn
Copy link
Contributor

jakedahn commented Feb 3, 2025

AMAZE!

Thank you for doing all of this!

--

I just tried it locally, I ran into a minor issue with a dependency issue for merkle-reference not existing in the jumble app, but is being used from common-charm. From what I could tell, this should all have just worked, but to get things working I had to add merkle-reference as a jumble dependency. Probably something funky with our pnpm setup, but I think that's fine for now, so just going to go ahead and merge 🚀🚀🚀

@jakedahn jakedahn merged commit f37ebcf into main Feb 3, 2025
3 checks passed
@jakedahn jakedahn deleted the feat/react-shell-exploration branch February 3, 2025 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants