Closed
Bug 1218913
Opened 10 years ago
Closed 9 years ago
Explicitly state types in json schemas, when possible
Categories
(Taskcluster :: General, defect)
Taskcluster
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pmoore, Assigned: pmoore)
Details
Attachments
(5 files)
|
61 bytes,
text/x-github-pull-request
|
jonasfj
:
review+
|
Details | Review |
|
56 bytes,
text/x-github-pull-request
|
jonasfj
:
review+
|
Details | Review |
|
55 bytes,
text/x-github-pull-request
|
jonasfj
:
review+
|
Details | Review |
|
56 bytes,
text/x-github-pull-request
|
pmoore
:
review+
|
Details | Review |
|
59 bytes,
text/x-github-pull-request
|
jonasfj
:
review+
|
Details | Review |
The golang taskcluster client relies on the type information in order to correctly assign types to properties. When a type is not given, it applies json.RawMessage which makes handling very cumbersome. We almost always can specify a type, so when we can, we should.
I'll hang bugs off this with PRs for the fixes.
| Assignee | ||
Comment 1•10 years ago
|
||
Oh boy, looks like we have 51 occurrences...
| Assignee | ||
Comment 2•10 years ago
|
||
When I do this, I'll also add a test to the go client so we get notified as soon as new types get added that don't specify a type...
Alternatively we could enforce this via schema validation...
| Assignee | ||
Comment 3•10 years ago
|
||
Attachment #8679586 -
Flags: review?(jopsen)
| Assignee | ||
Updated•10 years ago
|
Assignee: nobody → pmoore
| Assignee | ||
Comment 4•10 years ago
|
||
Attachment #8679588 -
Flags: review?(jopsen)
| Assignee | ||
Comment 5•10 years ago
|
||
Attachment #8679590 -
Flags: review?(jopsen)
| Assignee | ||
Comment 6•10 years ago
|
||
Attachment #8679614 -
Flags: review?(jopsen)
| Assignee | ||
Comment 7•10 years ago
|
||
Attachment #8679619 -
Flags: review?(jopsen)
| Assignee | ||
Comment 8•10 years ago
|
||
That's the lot - turned out to be less than 51 due to some duplication in the report I generated.
Thanks Jonas!
Updated•10 years ago
|
Attachment #8679586 -
Flags: review?(jopsen) → review+
Comment 9•10 years ago
|
||
Comment on attachment 8679590 [details] [review]
Github Pull Request for taskcluster-auth
Will rollout next I roll out something for auth...
Attachment #8679590 -
Flags: review?(jopsen) → review+
Comment 10•10 years ago
|
||
Comment on attachment 8679614 [details] [review]
Github Pull Request for taskcluster-queue
See issues on github PR...
Attachment #8679614 -
Flags: review?(jopsen) → review-
Comment 11•10 years ago
|
||
Comment on attachment 8679619 [details] [review]
Github Pull Request for task-graph-scheduler
landing this now..
Attachment #8679619 -
Flags: review?(jopsen) → review+
Comment 12•10 years ago
|
||
Comment on attachment 8679588 [details] [review]
Github Pull Request for taskcluster-index
Deployed...
Attachment #8679588 -
Flags: review?(jopsen) → review+
| Assignee | ||
Comment 13•10 years ago
|
||
Thanks for the reviews Jonas!
(In reply to Jonas Finnemann Jensen (:jonasfj) from comment #10)
> Comment on attachment 8679614 [details] [review]
> Github Pull Request for taskcluster-queue
>
> See issues on github PR...
Thanks - and well spotted! I've incorporated the corrections you made - can you review again?
| Assignee | ||
Comment 14•10 years ago
|
||
Comment on attachment 8679614 [details] [review]
Github Pull Request for taskcluster-queue
(updating r- => r+ to reflect r+ in GitHub PR after incorporating fixes)
Attachment #8679614 -
Flags: review- → review+
| Assignee | ||
Comment 16•9 years ago
|
||
I think all is done. Thanks Selena for following up. =)
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(pmoore)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•