Add ide tooling links to main guides #14505
Conversation
|
Thanks for your pull request! The title of your pull request does not follow our editorial rules. Could you have a look?
|
ghost
added
the
maxandersen
changed the title
| |Alpha | ||
| |Beta | ||
| |Stable (since 2019.3) | ||
| |Coming Soon! |
There was a problem hiding this comment.
this is from the original ide post made in 2019 - I didn't change these as I don't know what label you put on them today. Are they all just Stable?
There was a problem hiding this comment.
We started packaging Che stable releases with a Quarkus devfile since january 2019.
There was a problem hiding this comment.
cool - but at the time I asked che pm for when and looked at che.openshift.io I was informed it was not available to use/consume. I've changed it to stable now.
There was a problem hiding this comment.
You are right. I think we had resources problems on openshift.io at the time and the Quarkus sample didn't work at all.
|
|
||
| |Quarkus Code Snippets | ||
| |icon:check[] | ||
| |icon:times[] |
There was a problem hiding this comment.
As Quarkus Code Snippets are managed on LS server side all Quarkus toolings which are based on MP / Quarkus LS benefit with MicroProfile / Quarkus Code Snippets:
|Quarkus Code Snippets
|icon:check[]
|icon:check[]
|icon:check[]
|icon:times[]
|icon:check[]
| |icon:times[] | ||
| |icon:check[] | ||
|
|
||
| |Injection Discovery/Navigation |
There was a problem hiding this comment.
What do you mean about this feature? Could you explain more what is this feature please?
There was a problem hiding this comment.
intellij has features similar to what we had/have in jboss tools around find references like feature to navigate from a @Injection and similar annotations to possible sources and other way around.
There was a problem hiding this comment.
Thanks @maxandersen for your clarification. Do you think LSP4MP should support this feature?
There was a problem hiding this comment.
if feasible - there are quite the special cases to cover and getting UX for it working would be important. in jboss tools very few realized it was even there so almost not used.
| |icon:check[] | ||
| |icon:times[] | ||
|
|
||
| |Config editor |
There was a problem hiding this comment.
What do you mean with Config editor ? (syntax coloration?).
There was a problem hiding this comment.
editor that understands Quarkus properties. i.e. provide some quarkus specific content assist, validation, etc.
There was a problem hiding this comment.
If I understand correctly, Config editor = Config autocompletion + Config validation + ... I though Config editor was a section which provides other things than auto completion, validation.
There was a problem hiding this comment.
ah sure - so yeah, so does the tool have any kind of quarkus config editing facility beyond just a text editor with syntax highlighting.
we might actually want to add one for yaml vs properties.
| |icon:check[] | ||
| |icon:times[] | ||
| |icon:check[] | ||
|
|
There was a problem hiding this comment.
Config definition (navigation from properties file to Java definition) could be good to add too.
There was a problem hiding this comment.
you mean seeing where inside quarkus extension the config is defined ?
There was a problem hiding this comment.
There was a problem hiding this comment.
ack. added a line for it.
|
Totally makes sense to have this. Thanks. I'll let you discuss further with Eduardo to finalize it :). |
maxandersen
force-pushed
the
idetooling
branch
2 times, most recently
from
04b2907
to
e198466
Compare
Co-authored-by: Eduardo Ramirez <42619854+ebramirez@users.noreply.github.com> Co-authored-by: Mario Loriedo <mario.loriedo@gmail.com>
|
I applied the suggestions and squashed. |
Realized we didn't have the IDE work mentioned under main tooling
page. Starting by adding IDE overview from previous blog that we can maintain/expand
as needed.
Over time would be good to have a basic walkthrough per IDE but lets
add that incrementally as it will take some time.