Omar Kamel

Trying to get `this` type is incredibly unweildy. Ref: `Self` from Rust

1

Sometimes, I want to get "this" type. This is often side-stepped by the use of `covarient` in; for example; `didUpdateWidget(covarient ThisWidget oldWidget)` Additionally, I find myself occasionally wanting to do...

Combine Account and User transformers for consistency

1

fixes #5124 using pelican pr https://github.com/pelican-dev/panel/pull/423 Note: I do not have a setup to test this with, so I will need someone to review. That is why this is a...

**Is your feature request related to a problem? Please describe.** With mutations out, it may now be desirable to use simpler names in notifier functions like `delete` or... `update` However,...

**Describe the bug** `class Thing` and `_thing()` generates the same `String _$thingHash()`, causing a compilation error the hash itself is distinct, as expected, but the name conflict should not happen...

Let `Storage.inMemory` accept a map for initial test/mock data

1

Currently, `Storage.inMemory()` does not take any parameters. The constructor is useful for tests, as it does not require a real backend. However, If you wanted to ensure that some data...

Provide some means to generate from/toJson for compatible types for other code generators

4

json serializable is a powerful generator. Often, other generators will want to be able to generate to/fromJson functions for its own use. This can include retrofit, riverpod's v3 experimental `@JsonPersist()`,...

Generation failure on `copyWith`, despite being accessible.

5

**Describe the bug** Extending a freezed class breaks `copyWith` generation. The following error appears: ``` The class Foo2 requested a copyWith implementation, yet the parameter `value` is not cloneable. To...

Generation failure on `copyWith`, despite `copyWith` being disabled

1

**Describe the bug** Extending a freezed class breaks `copyWith` generation, at least previously. For that reason, I have it disabled. Despite doing so, the following error appears: ``` The class...

the signature for signal container is; `SignalContainer` However, looking at the actual code, `T` is never actually used, and actually resolves to `dynamic` by my code lens. For the sake...

the `evalContext` being a global variable makes sense in some ways, but it feels like its possible fragile or buggy when used with async gaps - surely the context changed...