Norbo11 / feedback_driven_development

For the Production Metrics project
6 stars 0 forks source link

Figure out how to properly handle an underlying function change and staleness propagation #17

Open Norbo11 opened 5 years ago

Norbo11 commented 5 years ago

Right now, we are only "stale" on a new commit.

The most conservative approach would mark everything stale as soon as a single character change is made.

Somewhere in between is using the PSI engine to propagate staleness to all callers of whatever we are editing. But this doesn't cover every scenario... try to come up with a counter example.