kestra-io / vscode-kestra

VSCode extension to bring Kestra's autocompletion to your IDE
Apache License 2.0
10 stars 0 forks source link

Refactoring & documentation implementation #12

Closed Skraye closed 10 months ago

Skraye commented 10 months ago

closes https://github.com/kestra-io/kestra/issues/2573 closes https://github.com/kestra-io/kestra/issues/2345

This PR bring documentation inside the VSCode editor, by the way some refactoring have been done. List of changes:

By default, we open the task one, at first it show a small information about how it works (clicking on a task) and a recall of every common properties for tasks, and when you click on a task, same as the actual kestra editor : image image

There is also a basic page that will explains the basics of a flow @anna-geller files are the markdown in the documentation folder so very easy if you wanna improve it! image

Skraye commented 10 months ago

@rldorado I've assign you if you want to take a look at what is our vs code extension and maybe you could give some advice!

Nico-Kestra commented 10 months ago

For me, the icon is okay since it's the same one used in the Help section for documentation.

rldorado commented 10 months ago

@rldorado I've assign you if you want to take a look at what is our vs code extension and maybe you could give some advice!

Thank you for adding me and let me learn about VSCode extensions are working. I've just added some minor tweak comments.

brian-mulier-p commented 10 months ago

I get a 2023-12-11 09:50:15,693 WARN default-nioEventLoopGroup-1-31 io.kestra.webserver.access [Date: 2023-12-11T09:50:15.683714709+01:00] [Duration: 9 ms] [Method: GET] [Url: /api/v1/plugins/null] [Status: 404] [Length: 103] [Ip: 127.0.0.1] [Port: 8080] call on every file change (on web only, standalone vscode seems not to do it) when I go on this flow

id: schedule12
namespace: company.team
tasks:
  - id: hello
    type: io.kestra.core.tasks.log.Log
    message: Kestra team wishes you a great day! 👋
triggers:
  - id: scheduler
    type: io.kestra.core.models.triggers.types.Schedule
    cron: "* * * * *"
    lateMaximumDelay: PT1S
disabled: true

I suspect the trigger to be the origin of it :thinking: