Realm generator rejects const values saying initialization must be const about realm-dart HOT 8 CLOSED

➤ PM Bot commented:

Jira ticket: RDART-992

from realm-dart.

Hi,

Same issue here, any workaround?

from realm-dart.

We're aware of this and will address it with a future release. Currently, the only known mitigation is to downgrade to 1.6. I'm sorry for the regression.

from realm-dart.

Apparently -1 is not a literal to the Dart analyzer

from realm-dart.

from realm-dart.

That looks like a great improvement. Unfortunately there are still some cases that cause false errors. Here is an example:

import 'package:dart_numerics/dart_numerics.dart' as numerics;
const int myconst = 1;
@RealmModel(ObjectType.embeddedObject)
class $Test {
  ObjectId id = ObjectId();
  int value1 = myconst;
  int value2 = numerics.int64MinValue;
}

If I comment out the new const test, this generates legal dart.

from realm-dart.

@derrickgw Thank you for your observation. I have created #1612 to handle value1 and value2.

But this const check was added explicitly to disallow ObjectId id = ObjectId(), so that is still not allowed.

Consider:

@RealmModel()
class _Stuff {
  ObjectId id = ObjectId();
}

Which is legal with realm_generator 1.9.0. If you look at the generated class, you will find that is illegal because it lifts the initializer expression and uses it as the default value of the optional parameter id on the generated constructor.

Stuff({
    ObjectId id = ObjectId(), // <-- this is not valid Dart, as default values must be const
  }) {

from realm-dart.

Wow. That was super fast. Thanks.

I see now that ObjectId has a constructor body, and calls DateTime.now(), so it can't really become a const class.

The previous database code generator I migrated from had a different paradigm that generated a Schema class instead of a child class, which allowed non-const default values, but had other limitations.

from realm-dart.