generate code for moor without null safety with build_runner

[salman731]

Hi,

I have use moor with json_serialization package when I generate code moor code generated without null safety but json_serialation emit following error

Generator cannot target libraries that have not been migrated to null-safety #823

pubspec.yaml

description: A new Flutter application.

# The following line prevents the package from being accidentally published to
# pub.dev using `pub publish`. This is preferred for private packages.
publish_to: 'none' # Remove this line if you wish to publish to pub.dev

# The following defines the version and build number for your application.
# A version number is three numbers separated by dots, like 1.2.43
# followed by an optional build number separated by a +.
# Both the version and the builder number may be overridden in flutter
# build by specifying --build-name and --build-number, respectively.
# In Android, build-name is used as versionName while build-number used as versionCode.
# Read more about Android versioning at https://developer.android.com/studio/publish/versioning
# In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.
# Read more about iOS versioning at
# https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
version: 1.0.0+1

environment:
  sdk: ">=2.7.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  # The following adds the Cupertino Icons font to your application.
  # Use with the CupertinoIcons class for iOS style icons.
  dropdown_search: ^1.0.3
  cupertino_icons:
  easy_rich_text:
  dio:
  flutter_svg:   # help us to use SVG in our ap
  dotted_border:
  flutter_screenutil: ^4.0.4+1
  uuid: #to generate unique ID's
  badges:
  barcode_scan2:
  bloc:
  flutter_bloc:
  splashscreen:
  mask_text_input_formatter: ^2.0.0 #for textfield formatter
  crypto: # for string conversions
  moor: ^4.2.1 # use the latest version
  sqlite3_flutter_libs: # Also use the latest version.
  custom_searchable_dropdown: ^1.0.5
  path_provider:
  path:
  provider:
  get: 4.0.0
  shared_preferences:
  back_button_interceptor:
  minimize_app:
  easy_localization:
  basic_utils:
  auto_size_text:
  tip_dialog:
  get_it:
  tuple:
  intl:
  after_init: ^0.1.2
  json_annotation: ^4.3.0
  csv: 4.0.2
  permission_handler: ^7.0.0
  flutter_email_sender: ^5.0.2
  sprintf:
  mailer:
  awesome_dialog: ^1.3.2
  file_picker:
  toast: ^0.1.5
  currency_formatter: ^1.1.0
  flutter_staggered_grid_view: ^0.4.0
  carousel_slider:
  moor_flutter:
  qr_code_scanner: ^0.4.0
  firebase_crashlytics: ^2.2.2
  flutter_staggered_animations: ^1.0.0
  flutter_svg_provider: ^0.1.9
  slide_item: ^1.0.8
  decimal:
  seekbar:
  flutter_xlider:
  #  audioplayer: ^0.8.1
  #  audioplayer_web: ^0.7.1
  flutter_hooks: ^0.18.0
  scrollable_positioned_list: ^0.1.10
  connectivity: ^3.0.6
  sizer: ^2.0.13
  linter:
  pedantic:
  socket_mobile: ^1.0.0
  pin_code_fields: ^7.3.0
  flutter_restart: ^0.0.3
  cron:
  internet_connection_checker:
  flutter_isolate:
  device_info: ^2.0.2
  package_info: ^2.0.2
  image: ^3.0.2
  barcode:
  screenshot:
  image_gallery_saver: ^1.6.9
  #  flutter_barcode_scanner:
  fluttertoast: ^8.0.8
  firebase_storage: 10.0.6
  audioplayer:

dev_dependencies:
  flutter_test:
    sdk: flutter
  moor_generator: any
  json_serializable: any
  build_runner:

# For information on the generic Dart part of this file, see the
# following page: https://dart.dev/tools/pub/pubspec

# The following section is specific to Flutter.
flutter:

  # The following line ensures that the Material Icons font is
  # included with your application, so that you can use the icons in
  # the material Icons class.
  uses-material-design: true

  # To add assets to your application, add an assets section, like this:
  assets:
    - assets/file/
    - assets/images/
    - assets/sound/
    - assets/icons/
    - assets/locales/
    - assets/barcode/
    - assets/app_images/
    - assets/app_images/scribes_loader.gif
    - assets/app_icons/
    - assets/app_icons/side_menu_icons/
    - assets/app_icons/setting_option_icons/
  fonts:
    - family: poppins
      fonts:
        - asset: assets/app_fonts/Poppins-Bold.ttf
          weight: 900
        - asset: assets/app_fonts/Poppins-SemiBold.ttf
          weight: 800
        - asset: assets/app_fonts/Poppins-Medium.ttf
          weight: 600
        - asset: assets/app_fonts/Poppins-Regular.ttf
          weight: 500
        - asset: assets/app_fonts/Poppins-Light.ttf
          weight: 300
    - family: cairo
      fonts:
        - asset: assets/app_fonts/Cairo-Bold.ttf
          weight: 700
        - asset: assets/app_fonts/Cairo-SemiBold.ttf
          weight: 500

[√] Flutter (Channel stable, 2.5.3, on Microsoft Windows [Version
    10.0.19042.1288], locale en-PK)
[!] Android toolchain - develop for Android devices (Android SDK
    version 30.0.3)
    X cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for
      more details.
    X Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK
      licenses.
      See
      https://flutter.dev/docs/get-started/install/windows#android-
      setup for more details.
[√] Chrome - develop for the web
[√] Android Studio (version 4.1)
[√] Android Studio (version 2021.1)
[√] VS Code (version 1.54.1)
[√] Connected device (4 available)

! Doctor found issues in 1 category.

[simolus3]

Generator cannot target libraries that have not been migrated to null-safety

Well, it's not drift/moor emitting this error so I'm not sure what I can do about this. json_serializable made the decision to only support null-safe code from a specific version (you could try downgrading), but drift continues to support generating code without null safety.

You could also do a partial migration to null-safety (add sdk: '>=2.12.0 <3.0.0' to your pubspec and a @dart=2.11 comment to each file). Then, migrate the files using json_serializable to null-safety only. But if you don't want to support null-safety I think the consequences is that you might not be able to use the latest versions of all generators.