apupier commented on code in PR #1085:
URL: https://github.com/apache/camel-website/pull/1085#discussion_r1374446050


##########
content/blog/2023/10/camel-language-server-kubernetes-context/index.md:
##########
@@ -0,0 +1,18 @@
+---
+title: "VSCode Language Support Autocompletion from Kubernetes Context"
+date: 2023-10-27
+authors: ["delawen"]
+categories: ["Tooling"]
+preview: "VSCode Language Support Autocompletion from Kubernetes Context"
+summary: "The Camel Language Server is now able to autocomplete configmaps and 
secrets coming from a Kubernetes connection."
+---
+
+Coming in the next VS Code Language support for Apache Camel, we are 
introducing a better context based autocompletion. We already had namespaces 
being auto completed when a related property was filled and there was a 
kubernetes connection configured. 
+
+Now the auto completion loads kubernetes context placeholders too as 
suggestions. On this case, it doesn't discriminate by name of the property or 
which camel connector we are configuring; it detects when a `{{secret:` 
or`{{configmap:` is being written as value in camel uri properties.
+
+<video loop="true" autoplay="true" 
src="https://user-images.githubusercontent.com/726590/273884659-c03020ae-bd5b-4328-a57c-d8aa7750e79f.webm";
 controls="controls" muted="muted" ></video>

Review Comment:
   have you tried to build the site locally?
   Last time I tried (several months if not years ago, the video were not 
working)



##########
content/blog/2023/10/camel-language-server-kubernetes-context/index.md:
##########
@@ -0,0 +1,18 @@
+---
+title: "VSCode Language Support Autocompletion from Kubernetes Context"

Review Comment:
   ```suggestion
   title: "VS Code Language Support Autocompletion from Kubernetes Context for 
secrets and configmaps"
   ```
   
   there was already completion for namespace, so I think we need to be a bit 
more specific in the title.
   
   VSCode --> VS Code



##########
content/blog/2023/10/camel-language-server-kubernetes-context/index.md:
##########
@@ -0,0 +1,18 @@
+---
+title: "VSCode Language Support Autocompletion from Kubernetes Context"
+date: 2023-10-27
+authors: ["delawen"]
+categories: ["Tooling"]
+preview: "VSCode Language Support Autocompletion from Kubernetes Context"
+summary: "The Camel Language Server is now able to autocomplete configmaps and 
secrets coming from a Kubernetes connection."
+---
+
+Coming in the next VS Code Language support for Apache Camel, we are 
introducing a better context based autocompletion. We already had namespaces 
being auto completed when a related property was filled and there was a 
kubernetes connection configured. 

Review Comment:
   it is already released :-) In Vs Code language Support 0.12.0



##########
content/blog/2023/10/camel-language-server-kubernetes-context/index.md:
##########
@@ -0,0 +1,18 @@
+---
+title: "VSCode Language Support Autocompletion from Kubernetes Context"
+date: 2023-10-27
+authors: ["delawen"]
+categories: ["Tooling"]
+preview: "VSCode Language Support Autocompletion from Kubernetes Context"
+summary: "The Camel Language Server is now able to autocomplete configmaps and 
secrets coming from a Kubernetes connection."
+---
+
+Coming in the next VS Code Language support for Apache Camel, we are 
introducing a better context based autocompletion. We already had namespaces 
being auto completed when a related property was filled and there was a 
kubernetes connection configured. 

Review Comment:
   ```suggestion
   Coming in the next [VS Code Language support for Apache 
Camel](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-apache-camel),
 we are introducing a better context based autocompletion. We already had 
namespaces being auto completed when a related property was filled and there 
was a Kubernetes connection configured. 
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to