Chromium Code Search - make it easier to find readers (VS writers) of a field |
||||
Issue descriptionRight now XRefs in Chromium Code Search can show references of a field. I would like to be able to find *only* readers (or only writers). For example - when trying to see how chrome::NavigateParams::disposition influences behavior I want to ignore code that sets this field - I am only interested in finding code that reads value of this field. I don't have a strong opinion on UX here. Xref filter would be one option, but I think it would be best to have separate subtrees - one of read references, one for write references (and one more for other things - like taking an address of a field? hmmm...).
,
Oct 24 2016
Also, it'd be nice to optionally hide (or collapse by default) unittest calls.
,
Oct 24 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 14 2018
Note that woxxom@'s request of filtering out unit test references can already be done in Chromium CS using Xref Filter > Exclude tests.
,
May 14 2018
,
May 16 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by emso@chromium.org
, Oct 24 2016