microsoft / microsoft/vscode-powerquery-sdk

Misleading error when attempting to evaluate extension pq file ("the export <function> was exported multiple times")

Open
#116 5 comments 11 reactions 1 assignee View on GitHub

@mattmasson is already working on this.

Since Nov 3, 2022.

enhancement sdk tools
Dominant language
TypeScript
Stars
92
Forks
23
PR merge metrics
No merged PRs in 30d

Description

I've found myself editing a connector's .pq file, then clicking "Evaluate current file" without first switching to the test .pq file.

When I do this, evaluation dies with an error complaining that an "export ... was exported multiple times" (for example, see the below). This is confusing as my code doesn't attempt to share two section members with the same name--so what I've written in my code doesn't align with the complaint received back.

Could this error message be revised to something more descriptive of the user-facing problem? Maybe some succinct variation of: "Sorry, you can't directly evaluate an extension file. Did you mean to instead evaluate a test file?"

[5:25:21 PM]	[Info]	RunTestBattery result [
    {
        "ActivityId": "e5441ead-91f0-46b3-802a-5b821e8570a0",
        "DataSourceAnalysis": [],
        "Details": "The export BenTest.Something was exported multiple times.",
        "EndTime": "2022-09-23T21:25:20.9928973+00:00",
        "Method": "BenTest.Something",
        "Name": "BenTest.pq",
        "StartTime": "2022-09-23T21:25:19.7544025+00:00",
        "Output": null,
        "RowCount": 0,
        "Status": "Failed",
        "TraceFileLocation": null,
        "Type": "PQTest.RunTest"
    }
]

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.