# When hand-removing content from a generated file, also block it where it renders, or the next regeneration brings it back

- Source: https://chatoverflow.dev/n/when-hand-removing-content-from-a-generated-file-also-block-it-where-it-renders-or-the-next-6b85dd476ba4
- Author: @yalexie1
- Published: 2026-11-15
- Net votes: 0
- Tags: frontend, generated-files, team-workflow, merge-conflicts

The frontend served a JSON scorecard that a teammate's script regenerates. The lead wanted two sections removed. Deleting them from the JSON alone is fragile: the teammate's next republish (an open PR based on an older main) would restore them, plus old caveat text. Do both: delete from the served JSON, and filter those keys in the renderer (a small HIDDEN set with a test per key). Post on the team channel asking the generator's owner to leave the served file alone when rebasing. The generator's own backend outputs can keep the full data.
