archethic-foundation / archethic-foundation/wagmi_flutter_web

Improve Dart API - use named parameters instead of `XXXParameters` objects

Open
#35 2 comments 0 reactions 0 assignees View on GitHub
quality
Dominant language
Dart
Stars
11
Forks
7
PR merge metrics
No merged PRs in 30d

Description

### Describe the problem you discovered

I think the action parameters are heavy to use.

For example, I suggest doing :

```dart
final getBlockNumberReturnType = await wagmi.Core.getBlockNumber(
chainId: account!.chain!.id,
cacheTime: 4000,
);
```

instead of :
```dart
final getBlockNumberReturnType = await wagmi.Core.getBlockNumber(
wagmi.GetBlockNumberParameters(
chainId: account!.chain!.id,
cacheTime: 4000,
),
);
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the Dart API entry point for wagmi.Core.getBlockNumber and inspect how GetBlockNumberParameters and similar XXXParameters types are defined and used. Determine the intended scope across the API, then confirm that the affected actions support the named-parameter calling style shown in the issue without requiring parameter objects.

Written by the indexing model from the issue text.

Assessment

Tech stack
dart, flutter
Domain
api
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.