jsx

Problem
I am returning to WebGL work after some time away (with Vulkan) so may be misinterpreting something here, but...
The WebGL example loops through the render_gl function every frame. Therefore it's recompiling the shaders, linking them, all of this work that doesn't need to be repeated in the render loop.

Steps To Reproduce
Steps to reproduce the behavior:
Start the app as

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

Scope

• This impacts ALL Mitosis outputs

To Reproduce
A link to a https://mitosis.builder.io/ fiddle containing the bug: link

Expected behavior
val2 should be

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>)}