Multiple Files - What is the best strategy to create a single wrapper or a single entry point?

[dinbtechit]

I am wondering what is the best strategy to create a single wrapper when you have multiple files.

flutter_rust_bridge_codegen \
  --rust-input "$REPO_DIR/native/src/api_1.rs" "$REPO_DIR/native/src/api_2.rs" \
  --dart-output "$REPO_DIR/lib/bridge_generated_api_1.dart" "$REPO_DIR/lib/bridge_generated_api_2.dart" \
  --class-name ApiClass1 ApiClass2 \
  --rust-output generated_api_1 generated_api_2

For the record, I use build.rs to generate the files. The above command is for understanding purposes only.

lib/
| - src/generated/
| - bridge_generated_api_1.dart
| - bridge_generated_api_2.dart
. . . (100 more files)

For example: when you generate everything into a single file it's easy to create something as shown below. But when you have hundreds of generated files. What is the best strategy to write a wrapper for this or a single entry point?

Singlefile:

DynamicLibrary createLibraryImpl() {
  const base = 'library_name';

  if (Platform.isIOS || Platform.isMacOS) {
    return DynamicLibrary.executable();
  } else if (Platform.isWindows) {
    return DynamicLibrary.open('$base.dll');
  } else {
    return DynamicLibrary.open('lib$base.so');
  }
}

// Usage:
LibraryName createLib() =>   createWrapper(createLibraryImpl());

---

The solution that I came up (see below) but this is basically not ideal and maintainable. Does anyone have a better approach for this?

fff.io

class ApiWrapper {

  DynamicLibrary createLibraryImpl() {
  const base = 'library_name';

  if (Platform.isIOS || Platform.isMacOS) {
    return DynamicLibrary.executable();
  } else if (Platform.isWindows) {
    return DynamicLibrary.open('$base.dll');
  } else {
    return DynamicLibrary.open('lib$base.so');
  }
 }

  /// A generic wrapper
  T createWrapperImpl<T>() {
    if (T is ApiClass1) {
      return ApiClass1Impl(createLibraryImpl()) as T;
     }  else if (T is ApiClass2) {
      return ApiClass2Impl(createLibraryImpl()) as T;
     }
     // ...  100 ApiClass. This does not seem like an ideal approach.

    throw Exception('Implementation not supported $T');
  }

  T getInstance<T>() {
    return createWrapperImplGeneric(externalLibrary) as T;
  }
}

// Usage:
ApiWrapper apiWrapper = ApiWrapper()
ApiClass1 get apiClass1 => apiWrapper.createWrapperImpl();
ApiClass2 get apiClass2 => apiWrapper.createWrapperImpl();
// ... 100 more instances.

[fzyzcjy]

Maybe related - #1024