value is t or nil.
The new colon-based alignment was also aligning colons in strings, as follows: (&img style:(+ "height:60px; width:60px; " "float:right; background-color:#FFF; " "padding:0.5px; margin:5px; " "border-radius: 16.67%; " "box-shadow: 0px 0px 1px #AAA;") src:(app artworkUrl60:)) This didn't seem good to me, so now colons inside strings are ignored for the purposes of alignment. (&img style:(+ "height:60px; width:60px; " "float:right; background-color:#FFF; " "padding:0.5px; margin:5px; " "border-radius: 16.67%; " "box-shadow: 0px 0px 1px #AAA;") src:(app artworkUrl60:))
1. The beautifier no longer applies fixed-width indentation for any symbols except for "class", which is indented by a single column. This (imo) provides less-distracting alignment and tightens up the left side of class declarations. 2. Labels (including selector components) are now aligned on their trailing colons.
I've been generating a lot of HTML with Nu and decided to take this simple extension from the Hiccup Clojure library. Now when we specify a markup element with the (&element) automatic operator, we can add classes and id values by including "." and "#" in the element name. Examples: % (puts (&div)) <div></div> % (puts (&div.x)) <div class="x"></div> % (puts (&div#main)) <div id="main"></div> % (puts (&div#main.x1.x2.x3)) <div id="main" class="x1" class="x2" class="x3"></div> Beware that this means that the '#' can now be included in symbols, so if you have code like "this#", you will be unpleasantly surprised by this change.
…bundle repo link
If you send the map: message to a dictionary and it will apply the provided callable to each value and return another dictionary with the results set for the corresponding keys. E.g.: % (set origin (dict "alpha" 10 "bravo" 20)) <__NSDictionaryM:7f9224202c50> % (set destination (origin map: (do (x y) (+ 1 y)))) <__NSDictionaryM:7f9224202f40> % (destination "bravo") 21
nubake accepts three new options: --method <methodname> --class <classname> --category <categoryname> When these are provided, nubake produces a source file that adds the named category to the named class. The category adds a method that evaluates the baked Nu code and returns the result. The purpose of this is to bake in code that can be evaluated from Nu. The code is evaluated in the main Nu parser's context so that macros and other objects can be made available to subsequent Nu code. Example: % nubake server.nu --method macros --category Baked --class MyServer --output MyServer+Baked.m
…labelValue method (deprecating labelName)
also fixed unit test that expected "Xcode" to be installed. It fails when a developer preview is installed instead (under a different name).