fuzdev / fuzdev/gro

types for `invoke_task`

Open
#520 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
19
Forks
0
Avg merge
1d 6h
Merged PRs (30d)
3

Description

One of the few rough edges I notice often in Gro these days is the lack of types for invoke_task.

  • generate types so task name string+params are checked against the project's tasks and their args (resolve all including gro's builtins)
    • maybe import task types using the same strategy as SvelteKit, tsconfig rootDirs with ./$types.js?
  • maybe invoke_task should optionally accept a task function reference? the string form allows you to transparently override builtins which I continue to like

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the invoke_task entry point and reviewing the proposed tsconfig rootDirs and ./$types.js strategy. Done means task names and parameters are checked against project tasks and Gro's builtins; the optional task-function reference is an unresolved design question.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.