You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a steiger.config.ts in the root of my project. I temporarily disabled a rule in my steiger.config.ts. When I run steiger ./src from the project root it ignores errors related to that rule. But when I enter a subfolder and then run steiger ../src it starts to report errors related to that disabled rule.
Seems like it only parses the working directory when searching for the config. Shouldn't it recursively go up through the folders to find a config?
The text was updated successfully, but these errors were encountered:
Interesting, I thought it already worked like that. However, I'm not sure how beneficial this feature is. We might consider that if you don't have the config in the current directory, you should specify the path explicitly. Idk. Or maybe we can just implement this behavior and not think too hard
I have a
steiger.config.ts
in the root of my project. I temporarily disabled a rule in mysteiger.config.ts
. When I runsteiger ./src
from the project root it ignores errors related to that rule. But when I enter a subfolder and then runsteiger ../src
it starts to report errors related to that disabled rule.Seems like it only parses the working directory when searching for the config. Shouldn't it recursively go up through the folders to find a config?
The text was updated successfully, but these errors were encountered: