Closed Bug 1899376 Opened 8 months ago Closed 8 months ago

Support chrome:// and resource:// link to not-indexed files

Categories

(Webtools :: Searchfox, task, P3)

task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: arai, Assigned: arai)

References

Details

Attachments

(1 file)

Currently chrome:// and resource:// links are supported only between indexed files (css, js, html, C++), given it depends on FILE_* target.
Other resources such as images are not linked.
They could be supported by modifying crossref to automatically generate target, or something along that line.

Yes, I think crossref likely makes the most sense. I'm not sure how much you've looked at the per-file-info stuff[1], but we do hold onto the per-file-info concise map throughout the entire crossref process. We could certainly flip a flag for each file as to whether we have analysis data for each file[2], and potentially whether we saw a file definition for it, and then at the end create file definitions for all the files missing it.

1: The https://github.com/mozsearch/mozsearch/pull/584 PR/commit may be of some minor interest to skim.

2: I don't know that we want to change our file listing display at this moment, but that might be an interesting bit of information to expose there eventually. It's probably most useful as a faceting/filtering mechanism, especially if we're trying to find cases where indexing is broken for files that would normally be indexed, etc. (Although I have proposed adding a diagnostic record in bug 1789515 which likely would be even more useful.)

Attached file GitHub Pull Request
Assignee: nobody → arai.unmht
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: