Closed
Bug 1353093
Opened 8 years ago
Closed 8 years ago
Expand GraphQL API to support Test-Group-Based UI
Categories
(Tree Management :: Treeherder: API, enhancement)
Tree Management
Treeherder: API
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: camd, Assigned: camd)
References
Details
Attachments
(2 files)
We can use the GraphQL API syntax to support the test based UI.
| Assignee | ||
Updated•8 years ago
|
Assignee: nobody → cdawson
Comment 1•8 years ago
|
||
| Assignee | ||
Comment 2•8 years ago
|
||
Comment on attachment 8854088 [details] [review]
[treeherder] mozilla:graphql-filtering > mozilla:master
Hey Will-- Are you up for reviewing this? If you're on to other things, no problem. Please reassign to Ed. Thanks! :)
Attachment #8854088 -
Flags: review?(wlachance)
Comment 3•8 years ago
|
||
Comment on attachment 8854088 [details] [review]
[treeherder] mozilla:graphql-filtering > mozilla:master
I don't mind reviewing this, but it's probably better if Ed does it from the perspective of knowledge transfer.
Attachment #8854088 -
Flags: review?(wlachance) → review?(emorley)
Updated•8 years ago
|
Attachment #8854088 -
Flags: review?(emorley) → review+
Comment 4•8 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/d85b8f74d2bd63a7bd1de420aa15f422b360dbc8
Bug 1353093 - Add GraphQL filtering (#2313)
* Bug 1353093 - Update Graphene to the latest version
* Bug 1353093 - Allow parent models to reference children of foreign keys.
This is needed for the GraphQL / Graphene implementation to be able to
filter child fields.
* Bug 1353093 - Add filtering to Push, Job and JobDetail GraphQL elements
This is in support of the TestGroup Based UI for fetching the exact data we
need to display in a single query.
| Assignee | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment 5•8 years ago
|
||
| Assignee | ||
Comment 6•8 years ago
|
||
Comment on attachment 8856756 [details] [review]
[treeherder] mozilla:camd-patch-1 > mozilla:master
I wasn't able to just make this change without a PR. I figure you could double-check it prior to merge? Seems a bit circular since you actually wrote this code... :)
Thanks again for all your help with this.
Attachment #8856756 -
Flags: review?(emorley)
Comment 7•8 years ago
|
||
Comment on attachment 8856756 [details] [review]
[treeherder] mozilla:camd-patch-1 > mozilla:master
Looks great! Many thanks :-)
Attachment #8856756 -
Flags: review?(emorley) → review+
Comment 8•8 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/8181a778aad118fe507f1c4e3a55c5ea22709ab4
Bug 1353093 - Make migration 0008 a no-op (#2334)
Django bug https://code.djangoproject.com/ticket/28065 causes the
addition of ``related_name`` to create a migration that will drop and
re-add the foreign key. However, this is a ``meta`` only change, so
no DB changes should be made and this ForeignKey drop and re-add
is super expensive. I didn't notice this problem before I merged
commit d85b8f74d2bd63a7bd1de420aa15f422b360dbc8.
You need to log in
before you can comment on or make changes to this bug.
Description
•