microsoft / microsoft/vscode-powerquery-sdk

[Feature] Add a tasks that makes it easy to validate the .mez file

Open
#298 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Preflight Checklist
Problem

It's possible to compile a connector without syntax errors, but have that connector fail to load in Power BI Desktop. Many of these errors can be detected by running the pqtest info command over the mez file.

Examples

  • Publish record not found (i.e. typo in name)
  • Data Source Kind path issues (i.e. multiple data source functions with different sets of required parameters)
Desired Solution

Built-in task to run the info command.
Could just return a pass or fail or return the full info result.
Could be run automatically after a build step.

Alternatives and Workarounds

You can manually run the pqtest.exe info command.

Additional Context

No response

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.

Research direction

No file or test is named in the issue. Start by running the existing pqtest.exe info command on a .mez file and then inspect how VS Code tasks and build steps are represented in this SDK. Done should be a built-in task that runs the info command and has an agreed pass/fail or full-output behavior, including whether it runs after builds.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
build-system, cli, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.