boot-clj/boot

Dynamic var to customize env at task creation time

Open

#468 建立於 2016年6月2日

在 GitHub 查看
 (8 留言) (0 反應) (0 負責人)Clojure (1,748 star) (178 fork)batch import
help wanted

描述

It would be nice to shadow the global env to better separate multiple apps running in the same boot pipeline. This shadowing is only needed at task creation time, not run time.

As discussed in Slack a dynamic var *env* (in boot.pod or boot.core) might be the solution.

;; binding *env* when creating the pipeline
(binding [*env* (get-env)]
  (my-task))

(deftask my-task []
  (fn [next-task]
    ;; bind env outside fileset-receiving fn
    (let [env *env*]
      (fn [fileset]
        (pod/make-pod env ,,,))))

/cc @micha @arichiardi

貢獻者指南

技術棧
無
領域
build systemtooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Understanding of Clojure dynamic variablesFamiliarity with boot pipeline and namespaces
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
The issue suggests introducing a dynamic var `*env*` in `boot.pod` or `boot.core` to allow shadowing the global env at task creation time. Research the boot source code in the `boot` and `boot.core` namespaces to understand how env is currently bound and used. Review the Slack discussion referenced in the issue for context. The implementation would likely involve defining a dynamic var and binding it in task creation functions, while ensuring backward compatibility.