Daco Harkes

Results 213 issues of Daco Harkes

**For v1.1, we need to be convinced that we don't need to break the API later.** **For v1.0, we need to be convinced that we don't need to break the...

package:hooks
package:hooks_runner

We should consider making `@Native`s automatically be mapped to `@ResourceIdentifier`s. `@Native`s have a `symbol` and `assetId` (both possibly inferred). https://api.dart.dev/stable/3.3.3/dart-ffi/Native-class.html `@ResourceIdentifier`s only have a `Object? metadata`. https://pub.dev/documentation/meta/latest/meta/ResourceIdentifier/ResourceIdentifier.html A possible mapping...

package:native_assets_cli
package:ffigen

This needs to be supported downstream: * https://github.com/dart-lang/sdk/issues/55377 * https://github.com/flutter/flutter/issues/146270 After we support adding assets in link hooks, we should update the doc comments on `link`. The current workaround is...

P3
package:native_assets_cli

The `hook/build.dart` is run _before_ kernel compilation. We should consider running a `hook/link.dart` after kernel compilation. In AOT we would have access to tree-shaking information that would enable us to:...

P1
package:native_assets_builder

Initially, we had the idea that the input and output for `build.dart` would be unstructured JSON/YAML, and that there would be multiple views on top of these JSONs. In this...

P2
package:native_assets_cli

We have support for macros that are direct constants: * https://github.com/dart-lang/native/issues/534 But maybe we can do better and try to support more expressions and macros referring to macros. * https://github.com/dart-lang/native/issues/1057#issuecomment-2031601888...

package:ffigen

I spent 0.5-1 hour per gardening shift clicking through tests that are meta-flaking. Most of them have: 1. Already an issue 2. A log that is textually similar to the...

results feed

When going to the history of a test, all kinds of comments show up that are not related to that test but to other test status approvals that happened to...

results feed

When using JSON/yaml configs and this package, at some point we read data out of the contents-agnostic cli_config and populate a specific config. Some examples: ```dart List _readFieldsFromConfig() { return...

package:cli_config

Do we want for everything 1. a custom parser, 2 a custom validator. For example, maybe one wants on accept `foo` and `bar` as values, but would like to transform...

type-enhancement
package:cli_config