Add @react.componentWithProps to MyWeirdComponent test

[nojaf]

I am slowly coming to terms with the potential limitation of the preserve-jsx feature, which may require @react.component or @react.componentWithProps.

[pkg-pr-new]

Open in StackBlitz

rescript

npm i https://pkg.pr.new/rescript-lang/rescript@7437

@rescript/darwin-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/darwin-x64@7437

@rescript/linux-arm64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/linux-arm64@7437

@rescript/linux-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/linux-x64@7437

@rescript/win32-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/win32-x64@7437

@rescript/darwin-arm64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/darwin-arm64@7437

commit: 637ffaf

[zth]

Yeah enforcing the @react.xx attribute sounds like a very reasonable requirement for preserve mode.

I think you in theory can also do this if you need the uppercase name:

  let \"MyWeirdComponent" = props =>
    <p>
      {React.string("foo")}
      {React.string(props.\"MyWeirdProp")}
    </p>
  
  let make = \"MyWeirdComponent"

That gives me this in the playground (without preserve mode though, so might be worth adding as a test as well):

function MyWeirdComponent(props) {
  return JsxRuntime.jsxs("p", {
    children: [
      "foo",
      props["\\\"MyWeirdProp\""]
    ]
  });
}

let MyWeirdComponent$1 = {
  MyWeirdComponent: MyWeirdComponent,
  make: MyWeirdComponent
};

let _escaped_jsx_prop = JsxRuntime.jsx(MyWeirdComponent, {
  MyWeirdProp: "bar"
});