From 63606f25b90d3580db500105e61cd46c6cae9156 Mon Sep 17 00:00:00 2001 From: jcberquist Date: Sun, 18 Dec 2016 21:01:37 -0500 Subject: [PATCH] Prepare for v0.21.0 - added context menu item for copying cfc dot path to clipboard - improved cfscript highlighting when it is embedded in a string --- messages.json | 4 ++- messages/0.21.0.txt | 63 +++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 66 insertions(+), 1 deletion(-) create mode 100644 messages/0.21.0.txt diff --git a/messages.json b/messages.json index 6505b20..54c2c31 100644 --- a/messages.json +++ b/messages.json @@ -31,5 +31,7 @@ "0.16.0": "messages/0.16.0.txt", "0.17.0": "messages/0.17.0.txt", "0.18.0": "messages/0.18.0.txt", - "0.19.0": "messages/0.19.0.txt" + "0.19.0": "messages/0.19.0.txt", + "0.20.0": "messages/0.20.0.txt", + "0.21.0": "messages/0.21.0.txt" } diff --git a/messages/0.21.0.txt b/messages/0.21.0.txt new file mode 100644 index 0000000..6b7049e --- /dev/null +++ b/messages/0.21.0.txt @@ -0,0 +1,63 @@ +CFML v0.21.0 Changelog: + +- Added a right click context menu item (Copy CFC Dotted Path) for when the + active view is a component, that copies the dot path to that component to + the clipboard. This functions in the same way is the context menu item when + right clicking on a CFC file in the side bar. + +- Syntax highlighting changes to remove string scope coloring from cfscript + embedded in strings. For example, in the following code: + + mystring = 'something #struct.key#'; + + `key` used to be colored as if it were a string, but this should no longer be + the case. + +- Miscellaneous bug fixes - see the recent GitHub commits for more information + + +It looks to me like I missed out on actually including the v0.20.0 changelog +when I pushed that version out, sorry! I have copied it in below, in case you +haven't seen it. + +CFML v0.20.0 Changelog: + +- Added the following tags to the default list of tags that do not receive a + closing tag: `cfcontent`, `cfparam`, `cfflush`, `cffile`, `cfdirectory`, + `cfheader`, `cfhttpparam`, `cflog`, and `cfimage`. + https://github.com/jcberquist/sublimetext-cfml/pull/58 + https://github.com/jcberquist/sublimetext-cfml/pull/59 + +- Component method completions are no longer of the form `method():returntype` + by default, as it turns out this format blocks Sublime Text from including + local buffer completions in the completion list. Instead the completion names + now only include the method name. It is possible to get the old completion + name style back via a new package setting `cfc_completion_names` - the + two options for it are "basic" and "full". (If this setting is changed, you + will need to run the `CFML: Index Active Project` command via the command + palette for the change to take effect for indexed components.) If you do want + to use the old completion style a plugin such as `All Autocomplete` can be + used as a workaround to get local buffer completions back into the completion + list. See the issue below for more discussion: + https://github.com/jcberquist/sublimetext-cfml/issues/57 + +- For Sublime Text builds 3116+ running the documention command on mouse hover + is now supported. This is enabled by default, but can be disabled by setting + the package setting `cfml_hover_docs` to false in your user package settings. + +- The documentation command now highlights the relevant regions of the code + to which the displayed documentation pertains. This is enabled by default, + but can be disabled by setting the package setting + `inline_doc_regions_highlight` to false in your user package settings. + +- When using the CFML formatting command to format the current function, it + will now format the function declaration as well as the function body. + +- When formatting a function call that contains an anonymous function, e.g.: + + myArray.map(function(item) { + return item.key; + }); + + the anonymous function will be kept inline with the opening parenthesis, + instead of always being placed on a new line.