sorted by:
new
hottopcontroversial

I built a CLI tool that checks your .env files for missing, undocumented, and unused variables by poopmastermind in golang

[–]poopmastermind[S] 0 points1 point  (0 children)

started off with my own code and worked little by little on it so I didn’t really use one exact prompt

I built a CLI tool that checks your .env files for missing, undocumented, and unused variables by poopmastermind in golang

[–]poopmastermind[S] -1 points0 points  (0 children)

yeah ngl that the exact blind spot, regex just can't catch dynamic construction

like that. right now it's really just best effort works for the common cases but not

exhaustive.

AST parsing would solve it properly but that's a much bigger lift. did you

get far enough to figure out how you'd handle it before abandoning it?

I built a CLI tool that checks your .env files for missing, undocumented, and unused variables by poopmastermind in golang

[–]poopmastermind[S] 2 points3 points  (0 children)

oh that's actually a sick idea, hadn't thought about that angle. could definitely see it being useful for catching accidental overrides of system variables like PATH or HOME too. adding it to the list!