Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[typespec] expose linter rule documentation url in codefixes #5131

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

mzhongl524
Copy link
Member

Modifications

best-practices:
1、Add a URL to the rule file to point to the relevant document.(for testing)

compiler:
1、A new codefix file has been added to handle the Linter Rule doc URL. 2、Added OPEN_RULE_DOC command type.
3、If the diagnostic URL is not empty, add a codefix and process the send request in the server file.

typespec-vscode:
1、Define the request and open the received URL document.

samples:
1、Add lint-related configurations to the yaml configuration file to define a lowercase model type in the tsp file for functional testing. Such as "model foo {}".

Related issues:#3043

1、Add a URL to the rule file to point to the relevant document.(for testing)

compiler:
1、A new codefix file has been added to handle the Linter Rule doc URL.
2、Added OPEN_RULE_DOC command type.
3、If the diagnostic URL is not empty, add a codefix and process the send request in the server file.

typespec-vscode:
1、Define the request and open the received URL document.

samples:
1、Add lint-related configurations to the yaml configuration file to define a lowercase model type in the tsp file for functional testing.
Such as "model foo {}".
@azure-sdk
Copy link
Collaborator

azure-sdk commented Nov 15, 2024

❌ There is undocummented changes. Run chronus add to add a changeset or click here.

The following packages have changes but are not documented.

  • typespec-vscode
Show changes

@azure-sdk
Copy link
Collaborator

You can try these changes here

🛝 Playground 🌐 Website 📚 Next docs

@RodgeFu RodgeFu added the ide Issues for VS, VSCode, Monaco, etc. label Nov 16, 2024
@@ -0,0 +1,10 @@
import { defineCodeFix } from "../diagnostics.js";

export function createShowLinterRuleDocUrlCodeFix(docUrl: string) {
Copy link
Member

@timotheeguerin timotheeguerin Nov 16, 2024

Choose a reason for hiding this comment

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

This shouldn't be a code fix. It doesn't actually fix anything. It would break a --fix-all flag. This is only relevant to ide and so just need to be injected when creating the Vscode actions.
We are already including the doc url in many other place this is just another(including already in the reported diagnostic to the ide - clickable link)

- typespec-vscode
---

[typespec] expose linter rule documentation url in codefixes
Copy link
Member

Choose a reason for hiding this comment

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

Remove the bracket scope. Those changelog are already scoped to the packages above.
And update accordingly with my other comment

…efix file, and restore the other codes to the original state.
) {
mutate(tspDiag.codefixes).push(
defineCodeFix({
id: "show-linter-rule-doc-url",
Copy link
Contributor

Choose a reason for hiding this comment

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

please extract the common string

Copy link
Member

@timotheeguerin timotheeguerin Nov 18, 2024

Choose a reason for hiding this comment

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

As comment above this still shouldn't even be a code fix and would simplify the logic later

for (const fix of tspDiag.codefixes ?? []) {
const currentCmd =
fix.id === "show-linter-rule-doc-url" ? Commands.OPEN_RULE_DOC : Commands.APPLY_CODE_FIX;
Copy link
Contributor

Choose a reason for hiding this comment

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

it's better to if-else the fix.id with their own logic to make the code more readable and also makes it easier to extend in the future

const docUrl = params.arguments?.[0] as string;
if (process.platform === "win32") {
// in windows
exec(`start ${docUrl}`);
Copy link
Contributor

Choose a reason for hiding this comment

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

please fix the security warning. And make sure these command are tested.

Copy link
Member

Choose a reason for hiding this comment

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

This will also only work on windows. Vscode is spice an open command that abstract that anyway

https://github.com/microsoft/vscode-eslint/blob/main/client/src/client.ts#L304-L305

vsDiag.codeDescription?.href &&
tspDiag.codefixes?.findIndex((x) => x.id === "show-linter-rule-doc-url") === -1
) {
mutate(tspDiag.codefixes).push(
Copy link
Member

Choose a reason for hiding this comment

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

This will still mutate the program . This most likely needs to be done later right when creating the vs code actions

) {
mutate(tspDiag.codefixes).push(
defineCodeFix({
id: "show-linter-rule-doc-url",
Copy link
Member

@timotheeguerin timotheeguerin Nov 18, 2024

Choose a reason for hiding this comment

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

As comment above this still shouldn't even be a code fix and would simplify the logic later

@@ -1,2 +1,9 @@
emit:
- "@typespec/openapi3"

linter:
Copy link
Member

Choose a reason for hiding this comment

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

Would revert that for now, best practice is not a published package and this would give the wrong impression looking at samples

…fix, and then define the command to open the URL
@@ -0,0 +1,54 @@
import vscode from "vscode";

const COMMAND = "CodeActionProvider.Custom.OpenUrl";
Copy link
Contributor

@RodgeFu RodgeFu Nov 20, 2024

Choose a reason for hiding this comment

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

it's better to use a more specific name: COMMAND -> OPEN_URL_COMMAND, "CodeActionProvider.Custom.OpenUrl" -> "typespec.openUrl"

);
}

export function createCommandOpenUrl() {
Copy link
Contributor

Choose a reason for hiding this comment

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

the command is not necessary coupling with CodeAction. please create a vscode-command file and move this there

/**
* Provides code actions corresponding to diagnostic problems.
*/
export class ExtensionCodeActionProvider implements vscode.CodeActionProvider {
Copy link
Contributor

Choose a reason for hiding this comment

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

TypeSpecCodeActionProvider

): vscode.CodeAction[] {
// for each diagnostic entry that has the matching `code`, create a code action command
return context.diagnostics
.filter((diagnostic) => typeof diagnostic.code === "object" && "target" in diagnostic.code)
Copy link
Contributor

@RodgeFu RodgeFu Nov 20, 2024

Choose a reason for hiding this comment

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

Shouldn't we check whether the diagnostic is for typespec and has url defined here?

.map((diagnostic) => this.createCommandCodeAction(diagnostic));
}

private createCommandCodeAction(diagnostic: vscode.Diagnostic): vscode.CodeAction {
Copy link
Contributor

Choose a reason for hiding this comment

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

the name is too general. better to be sth like "createOpenUrlCodeAction"

arguments: [
typeof diagnostic.code === "object" && "target" in diagnostic.code
? diagnostic.code.target.toString()
: "",
Copy link
Contributor

Choose a reason for hiding this comment

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

are we storing url in code.target? And we shouldn't add the codeAction if url is "".

],
};
action.diagnostics = [diagnostic];
action.isPreferred = true;
Copy link
Contributor

@RodgeFu RodgeFu Nov 20, 2024

Choose a reason for hiding this comment

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

I dont think this is a preferred codeaction

@@ -1,3 +1,5 @@
export const enum SettingName {
TspServerPath = "typespec.tsp-server.path",
}

export const OPEN_URL_COMMAND = "typespec.openUrl";
Copy link
Contributor

Choose a reason for hiding this comment

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

please move it to be with its command

diagnostic.source === "TypeSpec" &&
typeof diagnostic.code === "object" &&
"target" in diagnostic.code,
)
Copy link
Contributor

Choose a reason for hiding this comment

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

please add comment and check target is not empty

private createOpenUrlCodeAction(diagnostic: vscode.Diagnostic): vscode.CodeAction {
// The target will only exist if the compiler's diagnosis contains the url, so no data will be stored.
if (typeof diagnostic.code === "object" && "target" in diagnostic.code) {
const action = new vscode.CodeAction("Open Document", vscode.CodeActionKind.QuickFix);
Copy link
Contributor

Choose a reason for hiding this comment

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

please use Empty kind.

Copy link
Contributor

@mzhongl524 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ide Issues for VS, VSCode, Monaco, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants