You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2019/12/17 14:41:08 UTC
[camel-website] branch master updated: Re-add blogpost about
Language Support Tooling 0.0.20
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-website.git
The following commit(s) were added to refs/heads/master by this push:
new 4cde150 Re-add blogpost about Language Support Tooling 0.0.20
new 111754a Merge pull request #132 from apupier/ReaAddBlogpostForTooling
4cde150 is described below
commit 4cde1507edd15afd2ed872830021c32c21d0fc3b
Author: Aurélien Pupier <ap...@redhat.com>
AuthorDate: Tue Dec 17 15:09:32 2019 +0100
Re-add blogpost about Language Support Tooling 0.0.20
- policies allows to publish without linking to original blogpost (even
if not written publicly, it will be fixed soon)
- provide image with link to the youtube video
Signed-off-by: Aurélien Pupier <ap...@redhat.com>
---
.../CamelCatalogVersionPreference.gif | Bin 0 -> 225776 bytes
.../completionProperties.gif | Bin 0 -> 41988 bytes
.../diagnosticRangeImproved.png | Bin 0 -> 102476 bytes
.../filteredListOfQuickfix.gif | Bin 0 -> 134963 bytes
.../blog/LanguageSupportTooling-0.0.20/index.md | 48 +++++++++++++++++++++
5 files changed, 48 insertions(+)
diff --git a/content/blog/LanguageSupportTooling-0.0.20/CamelCatalogVersionPreference.gif b/content/blog/LanguageSupportTooling-0.0.20/CamelCatalogVersionPreference.gif
new file mode 100644
index 0000000..daaa01c
Binary files /dev/null and b/content/blog/LanguageSupportTooling-0.0.20/CamelCatalogVersionPreference.gif differ
diff --git a/content/blog/LanguageSupportTooling-0.0.20/completionProperties.gif b/content/blog/LanguageSupportTooling-0.0.20/completionProperties.gif
new file mode 100644
index 0000000..caed84c
Binary files /dev/null and b/content/blog/LanguageSupportTooling-0.0.20/completionProperties.gif differ
diff --git a/content/blog/LanguageSupportTooling-0.0.20/diagnosticRangeImproved.png b/content/blog/LanguageSupportTooling-0.0.20/diagnosticRangeImproved.png
new file mode 100644
index 0000000..af07aaa
Binary files /dev/null and b/content/blog/LanguageSupportTooling-0.0.20/diagnosticRangeImproved.png differ
diff --git a/content/blog/LanguageSupportTooling-0.0.20/filteredListOfQuickfix.gif b/content/blog/LanguageSupportTooling-0.0.20/filteredListOfQuickfix.gif
new file mode 100644
index 0000000..e129fb7
Binary files /dev/null and b/content/blog/LanguageSupportTooling-0.0.20/filteredListOfQuickfix.gif differ
diff --git a/content/blog/LanguageSupportTooling-0.0.20/index.md b/content/blog/LanguageSupportTooling-0.0.20/index.md
new file mode 100644
index 0000000..a333a8a
--- /dev/null
+++ b/content/blog/LanguageSupportTooling-0.0.20/index.md
@@ -0,0 +1,48 @@
+---
+title: "Language Support for Apache Camel - VS Code extension 0.0.20"
+date: 2019-12-16
+author: Aurélien Pupier
+categories: ["Tooling"]
+preview: Language Support for Apache Camel - VS Code extension 0.0.20
+---
+
+During the past months, several noticeable new features have been added to improve the developer experience of application based on Apache Camel. These updates are available in the [0.0.20 release of Visual Studio (VS) Code extension](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-apache-camel).
+
+Before going into the list of updates in detail, I want to note that I mentioned in the title the VS Code Extension release because VS Code extension is covering the broader set of new features. Don't worry if you are using another IDE, though, most features are also available in all other IDEs that support the Camel Language Server (Eclipse Desktop, Eclipse Che, and more).
+
+### Camel 3 inside
+
+Camel 3 was [released](https://camel.apache.org/blog/release-3-0-0.html) a few weeks ago, and the Camel Language Server is already relying on it internally. What does that mean for the end user? It means that the default catalog is now using Camel 3.
+
+If you are still based on Camel 2.x, no problem; check out the following awesome feature.
+
+### Camel catalog version options
+
+A parameter is now available to choose the Camel catalog version that you want. This can be specified in *File -> Preferences -> Settings -> Apache Camel Tooling -> Camel catalog version*.
+
+
+
+### Diagnostics with quick fixes and more precise range
+
+Diagnostics are really useful to pinpoint issues in our code. In previous versions, the diagnostic range error was provided on the full Camel URI. Now, for invalid component parameter keys and invalid component parameter enum values, the range is more precise and is pointing to the exact incriminated key or value.
+
+
+
+For unknown component parameter keys, there is also a quick fix provided if a component parameter key relatively similar exists. It is very useful in case of small typos.
+
+
+
+### Additional Camel components
+
+If you are using Camel components that are not part of Camel core catalog, it is now possible to provide the Camel component definition to have it fully supported by the tooling. The Camel component definition is defined as JSON. The JSON file can be found in the jar of the Camel component. The preference can be specified through *File -> Preferences -> Settings -> Apache Camel Tooling -> Extra-components -> Edit in settings.json*. Demo video [here](https://www.youtube.com/watch?v=U015RzlgFNM)
+
+
+### Properties file support
+
+Camel allows you to configure general component properties using a Properties file (see [here](https://github.com/apache/camel/blob/cfc9abf5f464057fa343a1a70a25a72c33c408bd/examples/camel-example-main/src/main/resources/application.properties#L42) for an example). Completion is available for component ids and component property keys.
+
+
+
+### What's next?
+
+This is very opened for the future. There will surely be improvements directed to Apache Camel K support. You can provide feedback on the [Camel Tooling GitHub repository](https://github.com/camel-tooling), it will help drive the future roadmap.
\ No newline at end of file