Thomas Beckmann

Reading through this I find https://github.com/epicmiller/es2015-default-class-properties a good approach. When trying I realized Backbone having build-in support for this. For example: ``` javascript class MyModel extends Backbone.Model.extend({ idAttribute: 'id' })...

@pdiniz13, does not look like this is in the repo. Could you contribute via a pull request?

Providing a PR as https://github.com/sivasamyk/logtrail/pull/428 on behalf of the changes of @soulis-siluos above.

Unlike the original report, that asked for the code to fetch all lazy-loaded attributes at once, I do believe the correct fix would be to fetch the yet unfetched attribute...

See also .

Not just LOBs but basic strings mapped to an ordinary varchar column. Last time I checked this behavior was present, still. This was the current version when I filed this...

To me the fetchgroups actually provide a lot flexibility, entity graphs won't work without. Wasn't even aware that can be disabled? Ah, by turning off that weaving option. Is there...

[jpa-lazy-basic-fields.zip](https://github.com/eclipse-ee4j/eclipselink/files/13560195/jpa-lazy-basic-fields.zip) Thanks @Zuplyx, find attached a minimal reproduction of the issue. The test fails because the changed but not yet persisted `newName` gets reset to the `oldName` when the `lazyVal`is...

This could be realized by supporting the more general feature https://github.com/google/json_serializable.dart/issues/1036.

Should cover most cases, except for enums one can not modify for some reason, but that's rare. Could be closed...?