Sometimes, when starting HttPlaceholder in a folder with an azure-pipelines.yml file for example, HttPlaceholder will interpret this file as stub and will also react when this file is updated, even though this file is not a valid stub file. We need to validate the file beforehand and not take the file into account when the file has been changed.
Maybe maintain a kind of blocklist of files that are definitely not stubs? E.g. azure-pipelines.yml, gitlab-ci.yml (don't know the CI files by heart, but this might be a solution).
Sometimes, when starting HttPlaceholder in a folder with an
azure-pipelines.ymlfile for example, HttPlaceholder will interpret this file as stub and will also react when this file is updated, even though this file is not a valid stub file. We need to validate the file beforehand and not take the file into account when the file has been changed.Maybe maintain a kind of blocklist of files that are definitely not stubs? E.g.
azure-pipelines.yml,gitlab-ci.yml(don't know the CI files by heart, but this might be a solution).