Feature: bring proxy-hint detection to the web profiler's compare (drift) view
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- html, javascript
- Domain
- frontend
Research direction
Start in assets/profiler-compare.js and the compare section of profiler.html around lines 297-383, then review the analogous single-dataset control in profiler-ui.js and the reusable FairCodeProfiler.proxyHints() in assets/profiler-engine.js. Call it for tableA and tableB with resultA.dimensions and resultB.dimensions, and confirm the compare view renders clearly labeled results for both datasets.
Written by the indexing model from the issue text.
Description
Where: assets/profiler-compare.js, profiler.html's compare section (lines ~297-383).
Current gap: #738 ported chi-squared proxy-hint detection to the web profiler, but only for the single-dataset view (profiler-ui.js's "Check for proxy columns" button, profiler.html:285-294). The compare/drift view has no equivalent, even though faircode compare --proxy-hints already computes proxy_hints_a/proxy_hints_b for both datasets separately (faircode/cli.py:465-473), and assets/profiler-engine.js already exposes a reusable proxyHints(table, dimensions, alpha) (added in #738) that just needs calling twice.
Repro:
$ grep -in "proxy" assets/profiler-compare.js
(zero matches)
Suggested approach: add a compareProxyHintsBlock/button analogous to the single-dataset one, calling FairCodeProfiler.proxyHints() against tableA/tableB with their respective resultA.dimensions/resultB.dimensions, and rendering two side-by-side (or A/B-labeled) result lists.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 2h 54m
- Merged PRs (30d)
- 59
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yakew7/Fair-Code
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
immich-app/immich#32426 ·
Maintainers usually reply within 1 day
-
todo type: feature
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
RocketChat/Rocket.Chat#42730 ·
Maintainers usually reply within 1 day
-
ai-driven-qa bug Cosmetic
Difficulty 1/5 Under an hour Newbie friendliness 90/100
linagora/cozy-settings#876 ·
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Chandraprakash-Darji/brick#79 ·
Maintainers usually reply within 1 day