Describe the bug
In some repositories, there are 'infrastructure' folders (.devenv, node_modules) with large numbers of files that are never going to contain a glossary.yml file. This can cause extensive delays on startup when scanning for glossary files.
Expected behavior
Any file/folder in a relevant .gitignore is ignored when scanning for glossary files. standard .gitignore semantics should apply (i.e. .gitignore in subfolders should apply to the subfolders of that location).
Is an 'override' facility needed to ensure a glossary file would be found/loaded even when in a .gitignore location? Probably not, since glossary file location is generally up to the developer, so should always be able to put it in a non-ignored location.
Additional context
Would also help with this issue, very likely, because it was double-discovering files in node_modules that were copied by an nx monorepo configuration
Describe the bug
In some repositories, there are 'infrastructure' folders (
.devenv,node_modules) with large numbers of files that are never going to contain aglossary.ymlfile. This can cause extensive delays on startup when scanning for glossary files.Expected behavior
Any file/folder in a relevant .gitignore is ignored when scanning for glossary files. standard .gitignore semantics should apply (i.e. .gitignore in subfolders should apply to the subfolders of that location).
Is an 'override' facility needed to ensure a glossary file would be found/loaded even when in a .gitignore location? Probably not, since glossary file location is generally up to the developer, so should always be able to put it in a non-ignored location.
Additional context
Would also help with this issue, very likely, because it was double-discovering files in
node_modulesthat were copied by an nx monorepo configuration