Angular2模块：最佳实践(Angular2 modules: best practices)

 首先，我同意您的评估，即请求解构通常属于路由处理程序定义。 Compojure提供Clojure解构语法的扩展这一事实似乎表明作者也有类似的感受。 
 
 您可以采取一些措施来减少解构表单中的重复。 首先，Clojure的标准地图绑定解构将有助于您发布的最后一条路线。 您可以做的第一件事是合并您从请求中提取的密钥:params ： 
 
(POST "/" {{title :title, tags :tags, content :content, privacy :privacy} :params ...} ...)
 
 这有点清楚，但是因为你没有重命名任何你要退出的值:params ，你可以做得更好： 
 
(POST "/" {{:keys [title tags content privacy]} :params ...} ...)
 
 这就是Clojure解构语法将为您提供的，但您可以利用Compojure的额外解构语法来进一步干扰它。 Compojure假设您最常感兴趣的是从请求的:params键获取值，因此您可以使用向量解析来将它们拉出来： 
 
(POST "/" [title tags content privacy] ...)
 
 好多了。 由于您仍需要从请求中获取其他值，因此您可以提供:as the-request绑定向量末尾的请求以直接访问请求： 
 
(POST "/" [title tags content privacy :as req] ...)
 
 但请记住，此变量也可以被解构。 考虑到所有这些，这是您上一个路线的简化版本： 
 
(POST "/" [title tags content privacy :as {{user-email :user-email} :session}]
  (home-post user-email title tags content privacy))
 
 我希望这有用！ 你写的Clojure越多，你就越能找到简化代码的方法，使它更清晰，更简洁。 

First off, I agree with your assessment that the request destructuring usually belongs with the route handler definitions. The very fact that Compojure provides an extension of Clojure's destructuring syntax seems to indicate that the author also felt similarly.
 
There are a couple of things that you can do to reduce duplication in your destructuring forms. First, Clojure's standard map binding destructuring will help with the last route you posted. The first thing that you can do is consolidate the keys that you are pulling from the request :params:
 
(POST "/" {{title :title, tags :tags, content :content, privacy :privacy} :params ...} ...)
 
That is a little clearer, but since you are not renaming any of the values that you are pulling out of :params, you can do better:
 
(POST "/" {{:keys [title tags content privacy]} :params ...} ...)
 
That is about as far as the Clojure destructuring syntax will get you, but you can take advantage of Compojure's additional destructuring syntax to DRY this up even more. Compojure assumes that you will most often be interested in getting values from the :params key of the request, so you can use vector destructuring to pull them out:
 
(POST "/" [title tags content privacy] ...)
 
Much better. Since you still need to get additional values out of the request, you can supply an :as the-request at the end of the binding vector to access the request directly:
 
(POST "/" [title tags content privacy :as req] ...)
 
Keep in mind, however, that this variable can also be destructured. With all of this in mind, here is a simplified version of your last route:
 
(POST "/" [title tags content privacy :as {{user-email :user-email} :session}]
  (home-post user-email title tags content privacy))
 
I hope that this is helpful! The more Clojure you write, the more ways you can find of simplifying code to make it clearer and more concise.