The new version 0.27 of \u201cFAKE \u2013 F# Make\u201d comes with new syntactic sugar for build targets and build dependencies. Don\u2019t be afraid the old version is still supported – all scripts should still work with the new version.<\/p>\n
Consider the following target definition:<\/p>\n
let<\/span> buildDir = ".\/build\/"<\/span><\/p>\n <\/p>\n Target "Clean"<\/span> (fun<\/span> _ -><\/span><\/p>\n CleanDir buildDir<\/p>\n )<\/p>\n <\/p>\n Target "Default"<\/span> (fun<\/span> _ -><\/span><\/p>\n trace "Hello World from FAKE"<\/span><\/p>\n )<\/p>\n <\/p>\n "Default"<\/span> <== ["Clean"<\/span>]<\/p>\n <\/p>\n run "Default"<\/span><\/p>\n<\/p><\/div>\n As you can see we are having a lot of \u201cmagic strings\u201d for the target names and the dependency definitions. This was always a small shortcoming in FAKE, since this doesn\u2019t allow refactoring and may result in runtime errors. <\/p>\n One of my goals for \u201cFAKE \u2013 F# Make\u201d is to remove these strings in future versions. Unfortunately this is not that easy, because it causes a lot of internal issues. In particular logging to the build server is much harder if you don\u2019t have a target name.<\/p>\n As posted in a bitbucket<\/a> comment by cipher<\/a> we could use the \u201cdynamic lookup operator<\/a>\u201d to remove some of the magic strings without breaking any internal code.<\/p>\n As a result we can rewrite the above sample as:<\/p>\n let<\/span> buildDir = ".\/build\/"<\/span><\/p>\n <\/p>\n Target? Clean <-<\/p>\n fun<\/span> _ -><\/span> CleanDir buildDir<\/p>\n <\/p>\n Target? Default <-<\/p>\n fun<\/span> _ -><\/span> trace "Hello World from FAKE"<\/span><\/p>\n <\/p>\n For? Default <- Dependency? Clean<\/p>\n <\/p>\n Run? Default<\/p>\n<\/p><\/div>\n All magic strings suddenly disappeared. I think this syntax looks really nice, but unfortunately the strings are not really gone, since the token Default<\/strong> is only checked at runtime.<\/p>\n Since the new syntax is really just syntactic sugar I\u2019m always interested in a better solution. Currently I\u2019m working on a syntax using monads. The result could look like this:<\/p>\n let<\/span> buildDir = ".\/build\/"<\/span><\/p>\n <\/p>\n let<\/span> Clean = target { CleanDir buildDir }<\/p>\n let<\/span> Default = <\/p>\n target { <\/p>\n trace "Hello World from FAKE"<\/span> <\/p>\n trace "Another line"<\/span><\/p>\n }<\/p>\n <\/p>\n Default <== [Clean]<\/p>\n <\/span><\/p>\n<\/p><\/div>\n Run Default<\/p>\n<\/p><\/div>\n This way the magic string are really gone, but my current problem is retrieving the target name from the let-binding name. Please leave a comment if you have an idea to solve this issue.<\/p>\n","protected":false},"excerpt":{"rendered":" The new version 0.27 of \u201cFAKE \u2013 F# Make\u201d comes with new syntactic sugar for build targets and build dependencies. Don\u2019t be afraid the old version is still supported – all scripts should still work with the new version. The problem Consider the following target definition: let buildDir = ".\/build\/" Target "Clean" (fun _ […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[23,448,546],"tags":[664,545,544],"_links":{"self":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/948"}],"collection":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/comments?post=948"}],"version-history":[{"count":1,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/948\/revisions"}],"predecessor-version":[{"id":949,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/948\/revisions\/949"}],"wp:attachment":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/media?parent=948"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/categories?post=948"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/tags?post=948"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/h5>\n
The first step<\/h5>\n
The idea for future versions<\/h5>\n