Right now, certain parts of our code base, like UnknownPathExcluder, will try to get the scaffold file mapping defined by drupal/core. If it doesn't exist, it will gracefully ignore it.
Should that be treated as an error condition? We generally can assume that Drupal core needs to scaffold some stuff, but if for some reason it doesn't, how should we react? Should we continue to ignore that? Throw an exception? Some combination of the two?
Active
3.0
Package Manager
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
I think we should throw an exception unless we can think of case where that would be valid. Our test would start to fail if core didn't use the feature any more