[Bug]: Inconsistency for task.id vs contextId or messageId
- Vorherrschende Sprache
- Shell
- Sterne
- 25.7k
- Forks
- 2.6k
- Ø Merge
- 3 T. 6 Std.
- Gemergte PRs (30 T.)
- 16
Beschreibung
### What happened?
In task object, the id is called `id` , that is inconsistent with other object like Message or Context or Artifact where the id is called messageId or contextId or artifactId. I suggest we have a more consistent naming for id field across all objects. I would prefer changing task.id to task.taskId .
### Relevant log output
```shell
```
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Beitragsleitfaden
Rechercherichtung
Find the Task object definition in the codebase, likely in a models or schemas directory. Compare with definitions for Message, Context, and Artifact to understand the current naming. Change the field from 'id' to 'taskId' in the Task class/struct and update all references. Run existing tests to ensure no regressions.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Bereich
- backend-api-design
- Issue-Typ
- Refactoring
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Aktivitätsstatus
- Veraltet
- Klarheit
- Klar beschrieben
- Anfängerfreundlichkeit
- 45/100