Skip to content

Bug 1846013 Allow users to fetch results from all frameworks - #9815

Open
gopar wants to merge 1 commit into
mozilla:masterfrom
gopar:bug-1846013-framework-param-optional-2
Open

Bug 1846013 Allow users to fetch results from all frameworks#9815
gopar wants to merge 1 commit into
mozilla:masterfrom
gopar:bug-1846013-framework-param-optional-2

Conversation

@gopar

@gopar gopar commented Aug 24, 2026

Copy link
Copy Markdown
Collaborator

Bug: API - make framework parameter optional

Note: This is a rewrite of #9761 since I mest up the git history there and found it easier to close and start a new one with the requested changes here.

@netlify

netlify Bot commented Aug 24, 2026

Copy link
Copy Markdown

Deploy Preview for treeherder ready!

Name Link
🔨 Latest commit 3d25ed2
🔍 Latest deploy log https://app.netlify.com/projects/treeherder/deploys/6a8caf02a823d90009b49671
😎 Deploy Preview https://deploy-preview-9815--treeherder.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

base_sig_id = base_sig.get("id", None)
new_sig = comparison_inputs.new.signatures_map.get(sig_identifier, {})
new_sig_id = new_sig.get("id", None)
sig_framework_id = base_sig.get("framework_id") or new_sig.get("framework_id")

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here:

  • When a framework is provided, base and new signatures are filtered to it, so they always share that framework, so or operation is benign.

  • When omitted (all frameworks), the comparison key doesn't include the framework, so the two sides can potentially differ and this matters for creating the graph links since it'll use one framework for both new/base.

I can try and create the graphs individually? Or another solution?



# Flag to denote that we should return results for all frameworks
LIST_ALL_FRAMEWORKS = -1

@gopar gopar Aug 24, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using -1 since PKs cannot be negative (unless we set it manually but i didn't see anything related to that here - please correct me if I'm wrong). And in the frontend we can map an "all" option to -1, so we don't have to update the serializers on the backend as well. This solves :sparky comment about using all string.

@gopar
gopar requested a review from gmierz August 24, 2026 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant