Changing the chompfile.toml while watching via chomp -w does not invalidate

[canadaduane]

I modified the chompfile while using chomp -ws and I was expecting it to re-build targets affected by the task whose options I modified:

[[task]]
  name = "build:html"
  template = "jspm"
  target = "lib/index.html"
  deps = ["src/index.html", ":build:svelte", ":build:typescript"]
  [task.template-options]
    env = ["browser", "production"]
    preload = true
    integrity = true

I added whitespace = false to the template-options, expecting index.html's import map to be formatted differently.

[canadaduane]

I may have tested this incorrectly. My chomp -ws command probably should have been chomp build -ws.

[guybedford]

Changes to the Chompfile is quite tricky to support, because it means modifying the in-place task graph based on a chompfile diff. So we would effectively need to implement a diffing algorithm which can be translated from a diff on the chompfile into a diff on the task graph, and then also make allowance for irreconcilable diffs to cause a complete reload. Definitely agreed this would be a good goal, will leave this up to track.

[canadaduane]

Would it be easier to exec/replace the running chomp process if the chompfile is modified? Mar 14, 2022 10:29:47 PM Guy Bedford ***@***.***>:

…

Changes to the Chompfile is quite tricky to support, because it means modifying the in-place task graph based on a chompfile diff. So we would effectively need to implement a diffing algorithm which can be translated from a diff on the chompfile into a diff on the task graph, and then also make allowance for irreconcilable diffs to cause a complete reload. Definitely agreed this would be a good goal, will leave this up to track. — Reply to this email directly, view it on GitHub[#92 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAAABAPHKVT4H2G6UORFDOLVAAG3HANCNFSM5QW7LCYA]. Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub]. You are receiving this because you authored the thread. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADwAAAA8CAYAAAA6/NlyAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAkSURBVGiB7cExAQAAAMKg9U/taQmgAAAAAAAAAAAAAAAAAABuOHwAAW17XWMAAAAASUVORK5CYII=###24x24:true###][Tracking image][https://github.com/notifications/beacon/AAAABAPINLUFBZ4TE4F63IDVAAG3HA5CNFSM5QW7LCYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOH6QY5CY.gif]

[guybedford]

I don't think I've ever written anything to replace the current process with a new invocation of itself? I would need to do more careful book-keeping to multi-instance the application lifecycle unfortunately :(

[guybedford]

(but yes you are right that's the way to do it)