Closed celesteking closed 3 years ago
Let's discuss!
I'm not a fan of the name "SLOWWATCH." What you're doing here isn't watching at all but polling.
No shit captain. Have you read the docs? What about all these stuck tests btw?
Anyway, is the varname the only thing that annoys you?
No shit captain. Have you read the docs?
Yes.
I think the 'on' trigger needs to have pull_request added. I'm making that change in another PR.
This PR seems abandoned. It doesn't pass lint tests and has no activity in half a year. If it were updated to pass the CI tests and replace the very long-winded explanation of motivation (you can document that here and link to it if you wish) with a succinct "this is how it works," paragraph, I'd be inclined to merge.
It's the first time ever I see a patch being rejected on basis of containing too much documentation. Usually, it's the other way around. We won't get far with such attitude.
It's the first time ever I see a patch being rejected on basis of containing too much documentation.
It's not. This PR hasn't been merged because it is failing lint tests. I told what you what I want to see before I merge it. There are others with merge access who may not mind wading through a wall of text to find the docs for the config options.
We won't get far with such attitude.
You have certainly demonstrated that. You asked for discussion but have been hostile towards it.
And curiously, you introduce env vars after calling them a security disaster in #39
override watch behavior by ENV vars
HARAKA_CONFIG_CUSTOM_DIR
sets custom config dirHARAKA_CONFIG_SLOWWATCH
selects slow watch behaviorA fix for the case when file is gone but
config.get
keeps returning pre-deletion data from cache.