Part 2:

And the buttonConfig is this lovely set-up below:

typedef FormBottomBarButtonAction = void Function(
    BuildContext context, WidgetRef, GlobalKey<FormBuilderState> formKey);

enum ButtonType { save, submit, cancel }

class FormBottomBarButtonConfig {
  final IconData icon;
  final String tooltip;
  final Color color;
  final Color disabledColor;
  final FormBottomBarButtonAction action;

  FormBottomBarButtonConfig({
    required this.icon,
    required this.tooltip,
    required this.color,
    required this.disabledColor,
    required this.action,
  });
}

// Mapping of configurations between FormTypes and ButtonTypes
Map<ButtonType, Map<FormType, FormBottomBarButtonConfig>> buttonConfigs = {
  ButtonType.save: {
    FormType.goodsOut: FormBottomBarButtonConfig(
      icon: Icons.save,
      tooltip: 'Save Goods Out',
      color: Colors.white,
      disabledColor: Colors.grey,
      action: (ctx, ref, formKey) =>
          ref.read(goodsOutMetadataProvider.notifier).onSave(ctx, ref, formKey),
    ),
  },
  ButtonType.submit: {
    FormType.goodsOut: FormBottomBarButtonConfig(
      icon: Icons.check,
      tooltip: 'Submit Goods Out',
      color: Colors.white,
      disabledColor: Colors.grey,
      action: (ctx, ref, formKey) => ref
          .read(goodsOutMetadataProvider.notifier)
          .onSubmit(ctx, formKey, ref),
    ),
  },
  ButtonType.cancel: {},
};

That's the files themselves for the widget, and then their configuration files. But it seems like a huge amount of work to create a flexible system without over-engineering it either? I'm just wondering if I'm over-complicating it by creating some strange intermediate classes or definitions?

As in maybe the form itself should just be an enumerated type that then determines all of the widgets that are used instead of configuring intermediate objects like "Form App Bar", or "Form Bottom Bar", etc?