Skip to content

Conversation

@CsCherrYY
Copy link
Contributor

Since vscode-java has adopted the language status item, we'd better update our tutorial here.

cc: @nickzhums

Signed-off-by: CsCherrYY [email protected]

|<i class="codicon codicon-bold"></i>|bold|
|<i class="codicon codicon-book"></i>|book|
|<i class="codicon codicon-bookmark"></i>|bookmark|
|<i class="codicon codicon-bracket-dot"></i>|bracket-dot|
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this codicon can be found here: microsoft/vscode#134102 (comment), it's already on vscode codicon repository.

@nickzhums
Copy link
Member

LGTM - Should we mention the three features it contains? eg. build status, pom file, etc

@CsCherrYY
Copy link
Contributor Author

LGTM - Should we mention the three features it contains? eg. build status, pom file, etc

IMO it's more important to let users know we have supported the language status item in Java than what is included in this item, since it's simple enough to find the features and the language status item is the common place for other languages as well.

If you think we should put a standalone section here. I can also add it🙂

@nickzhums
Copy link
Member

LGTM - Should we mention the three features it contains? eg. build status, pom file, etc

IMO it's more important to let users know we have supported the language status item in Java than what is included in this item, since it's simple enough to find the features and the language status item is the common place for other languages as well.

If you think we should put a standalone section here. I can also add it🙂

makes sense, let us keep it this way for now

@gregvanl gregvanl added the java label Apr 25, 2022
@gregvanl gregvanl self-assigned this Apr 25, 2022
@gregvanl gregvanl merged commit da105c6 into microsoft:main Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants