EotT123
EotT123
**Describe the bug** Extension methods are a great way to deal with nullness, eg see the example [here](https://github.com/manifold-systems/manifold/blob/master/manifold-deps-parent/manifold-ext/README.md#static-dispatching): ```java public static boolean isNullOrEmpty(@This CharSequence thiz) { return thiz == null...
Enhance the `create` methods for SQL objects by offering more flexibility for handling foreign keys. Currently, users have to choose between object references or IDs, but not a mix of...
This pull request enhances the `create` methods for SQL objects by offering more flexibility for handling foreign keys. Previously, users had to choose between object references or IDs, but now...
Like Manifold, Lombok also supports extensions (in a different way). I'm in favor of the Manifold-way, but I've found a case that I think isn't possible with Manifold (or is...
Lombok's [RequiredArgsConstructor](https://projectlombok.org/features/constructor) is a convenient tool for generating constructors without the need to manually write boilerplate code. However, this functionality encounters issues when used with Manifold properties. Fields annotated with...
Could it be possible to add lazy initialized fields when using properties? (similar to Lombok's [`@Getter(lazy=true)`](https://projectlombok.org/features/GetterLazy) The same syntax could be used, e.g. `@val(lazy = true) Object object = ;`....
Objects that are only used in a String Template are marked as unused.   Also applies to method parameters: 
Abstract properties are not being marked as used.   
When using Manifold properties, there is no way to find usages of a field that still uses a normal getter. ```java public class Foo{ @val String bar; } ``` ![screenshot...
When using Manifold properties, annotating a field with `@val` makes the field final. However, when using that field in a synchronized block, I get a warning message: `Synchronization on a...