Skip generated names, data formats and long json/xml at index time - #183
Merged
Merged
Conversation
A translation bundle like i18n/generated-de-CH.json matched every domain word in a question and outranked the code. The selector now skips by name (generated in a basename or segment, i18n/, locales/, __snapshots__/, generator suffixes, .lock/.sum), by format (csv, source maps, snapshots, translation catalogues, svg) and json/xml above a data ceiling, 8 KiB by default via BACKEND_INDEX_MAX_DATA_FILE_BYTES; manifests are exempt and yaml is never capped. The boot sweep re-applies every path-and-size rule, not only the operator's globs, so a new rule retires what an older build embedded, with the matching skip reason on the row.
…s a word, tag markers only Hand-written src/i18n/index.ts, GeneratedIdEntity.java and a README saying "auto-generated" were caught. Spring, JPA, logging, appsettings and Camunda bpmn20.xml join the ceiling exemptions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A translation bundle like i18n/generated-de-CH.json matched every domain word in a question and outranked the code.
The selector now skips by name (generated as a word of the basename or a segment, catalogue formats under i18n/ or locales/, snapshots/, generator suffixes, .lock/.sum), by format (csv, source maps, snapshots, translation catalogues, svg) and json/xml above a data ceiling, 8 KiB by default via BACKEND_INDEX_MAX_DATA_FILE_BYTES. Manifests and hand-written config that outgrows it (pom.xml, package.json, applicationContext.xml, appsettings*.json, bpmn20.xml) are exempt; yaml is never capped. Sizes in docs/measurements/2026-09-17-data-file-cap.md.
The boot sweep re-applies every path-and-size rule, not only the operator's globs, so a new rule retires what an older build embedded, with the matching skip reason on the row.