jsx

Environment:

• Yew version: 0.19
• Web-sys version 0.3.56
• Rust version: 1.59.0 stable
• Target: wasm32-unknown-unknown
• Build tool: trunk
• OS: Ubuntu 20.04
• Chrome 100.0.4896.60 (Official Build) (64-bit)

I spent a long time going around in circles trying to get a handle for the html element I'm interacting with so that I can do some further processing. After a lot of

The Storybook API has changed quite a lot since Solid's Storybook docs were written in 2019. It would be really helpful (and I think go a loooong way toward helping drive adoption, long-term) if Solid could:

1. Update the docs to reflect the latest Storybo

For the most part this just works, but functions within tagged markup get weird indent assertions, e.g.,

        ${collection.map((item) => {
          const { prop1, prop2 } = workWith(item);  // eslint: expected indentation of 4 but found 10 (indent)
          return html`  // eslint: expected indentation of 4 but found 10 (indent)
            <${Widget} prop1=${prop1} prop2=${prop2} />

I'm sorry to post an issue that is missing crucial evidence, but some debugging of a recent config loading bug makes me suspect that the react-rails railtie.rb may be modifying the load order of initializers, and preventing the values in Rails.application.config being as expected.

Whether this happens or not appears to be partly dependent on where in the Gemfile the react-rails gem is l

Repo: https://github.com/codercatdev/mitosis-example

Video Exmaple: https://youtu.be/fFjzpB3JkwU

I would expect this to default to reacts own state useState

 mitosis compile --to=react component.lite.jsx > output/component.jsx

We should be able to use dispatchEvent to define callback prop based onevent APIs, so we don’t have to deal with capturing/bubbling for specific events.

function MyComponent({id}) {
  const onclick = () => {
    this.dispatchEvent(new CustomEvent("customclick", {detail: {id}}));
  };
  
  return (
    /* children */
  );
}

// Usage

<MyComponent oncustomclick={(e

Blocked By: wix/vscode-glean#97

Example:

class Foo extends Component {

  render() {
    return (<div>
      {this.props.foo.map((bar) => <div>{bar.x}</div>)}
    </div>)
  }
}

Current:

 const Foo = props => {
   const foo = useRef();
   const x = useRef();
   return <div>
       {foo.current.map(bar => <div>{x.current}</div>)}