rnmbxcodegen

[mfazekas]

Fight RN codegen with more codegen.

See also reactwg/react-native-new-architecture#199

Using swift and RN with new architecture but providing compatibility with old arch requires an insane amount of boilerplate code. See required files.

We attempt to work around this using the schema.json generated by RN codegen and generating as many boilerplate as possible with ejs templates. Ejs templates can have grey-matter metadata in comments in the front.

To run the codegen:
1.) Run combine-js-to-schema-cli to create the schema.json used internally by react native codegen tool

cd example
mkdir -p ../tmp/generated
node ./node_modules/@react-native/codegen/lib/cli/combine/combine-js-to-schema-cli.js --platform android ../tmp/generated/schema.json ../src/specs/

2.) Run rnmbxcodegen

 npx bun ./scripts/rnmbxcodegen/rnmbxcodegen.ts

Pros:

• we can create new components faster
• we can refactor boilerplate code a bit easier by changing codeine

Cons:

• more complexity of codegen

Boilerplate:

• Foo.swift (implements the component in Swift)
• FooComponentView.mm and .h - (for new architecture - implements a view wrapping Foo in contentView)
• FooManager.mm, and FooManager.swift (RCTViewManager - implements methods on the view, I think only for old arch)
• FooModule.h, FooModule.mm - forwards methods to the FooManager

On android it's better only 3 files:

• FooManager.kt
• Foo.kt
• FooModule.kt

[FrederickEngelhardt]

Curious why is this file needed vs a kotlin file? Looks painful to support this syntax too.

Is this required for turbo modules to work in a library? Also is this auto-generated? Some of the iOS files say this, but not here 🤷 .