Invalid paths must not be ignored silently
The following discussion from !12 (merged) should be addressed:
-
@alossent started a discussion: This is the behavior we want, thanks! However that should not happen silently.
- for code maintenance, we need comments to explain why we ignore paths that either don't look like valid site paths or are not sanitized.
- for support, at a minimum we need to log when we encounter an invalid path. I suggest a
log.Warn()
with details about the webeossite being processed for each failure case (path is not a file path, or is not sanitized).