Feature Description
Hello,
Let's say I'm using Konsistent to define what my project directory and subdirectory and files look like, after I do that using MustHave, I want to also make Konsistent warn or error anytime there's an folder or file existed that wasn't defined in my musthave array and definition.
This way Konsistent can prevent things to exist that developer is unaware of, or AI agent create a file or folder and in somewhere where it should not exist or happen.
Otherwise without this feature or capability, Konsistent cannot be a strict or guarding tool, things could go out of rail.
Suggested Implementation
No response
Activity
2
barziahmed1mo ago@felixarntz, we can use flexible file and folder patterns to allow in komsistent, I'm not saying to define exactly all file with their names.
About test files, I don't know i colocate my test files with next to their file and enforce it in konsitent to expect such colocation of test files.
As i said, in konsistent we can define a high-medium architecture and structure design of our directory and enforce it, but without having check that finds anything goes out of defined structure, konsistent would be pretty weak and unfortunately not too much useful.
Think like allowlist based firewall, like deny by default firewall, not like denylist firewall where you check for what's blocked, and if not in blocklist then allow packet, this is of course against the principles
@barziahmed I like this idea. one follow-up question: Do you expect it to flag literally any new TypeScript file added outside of the
konsistent-controlled locations? how about adding test files? or adding little dev ops utility scripts that don't belong to the production code of the project?I'm just wondering whether the broad approach is reasonable - it would require you to control literally all possible TypeScript paths you may want to have via
konsistent, even non-production code patterns like the above.If you could share an example of how you envision this, that would be really helpful.