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
It'd be cool if blocks could only be updated every so often, so as to prevent long operations from being run all the time. For example, in our product markdown-inject runs on precommit, but it could be beneficial to have some emitted blocks of some components' npm run build output. It's not really something that changes so often that it need be evaluated every time, but running it every month or two could be nice.
To reduce complication / dependencies, the debounce property could instead take a number of minutes (43200), seconds (2592000), milliseconds (2592000), or something.
Then, markdown-inject would automatically inject a last-update property into the JSON config when it runs for that block:
It'd be cool if blocks could only be updated every so often, so as to prevent long operations from being run all the time. For example, in our product
markdown-inject
runs onprecommit
, but it could be beneficial to have some emitted blocks of some components'npm run build
output. It's not really something that changes so often that it need be evaluated every time, but running it every month or two could be nice.To reduce complication / dependencies, the
debounce
property could instead take a number of minutes (43200), seconds (2592000), milliseconds (2592000), or something.Then, markdown-inject would automatically inject a
last-update
property into the JSON config when it runs for that block:Preferably this date would be captured with
new Date().toISOString()
so the date is both easily machine parseable, but also decently human readable.The text was updated successfully, but these errors were encountered: