Control mez output file name
@mattmasson is already working on this.
Since Apr 5, 2024.
Assessment
This issue has not been assessed yet.
Description
Preflight Checklist
- I have installed the latest version of Power Query SDK.
- I have checked existing resources, including the common issues and the release notes.
- I have searched for similar issues.
Power Query SDK
0.3.1
Regression From
No response
Platform
Windows
Architecture
x64
OS Version
No response
VSCode version
No response
PQSdkTool Path
No response
Bug Description
In my .vscode/settings.json I have changed the name for the mez file:
"powerquery.sdk.defaultExtension": "${workspaceFolder}\\bin\\AnyCPU\\Debug\\NotSameNameAsDirectory.mez",
I have also changed my .proj file PropertyGroup
<PropertyGroup>
<OutputPath Condition="'$(OutputPath)' == ''">$(MSBuildProjectDirectory)\bin\AnyCPU\Debug\</OutputPath>
<IntermediateOutputPath Condition="'$(IntermediateOutputPath)' == ''">$(MSBuildProjectDirectory)\obj\</IntermediateOutputPath>
<MezIntermediatePath>$(IntermediateOutputPath)MEZ\</MezIntermediatePath>
<MezOutputPath>$(OutputPath)NotSameAsDirectory.mez</MezOutputPath>
</PropertyGroup>
However, when I run the build task MakePBX the generated mez file name is the parent directories name.
Steps to Reproduce
- Create new extension project, in a folder called
bug-folder - update the
.vscode/settings.jsonto have a new mez file name,CoolName.mez - update the
.projfile and change theMezOutputPathto also have theCoolName.mez
Actual Experience
bug-folder.mez is created instead of CoolName.mez
Expected Experience
No response
Additional Context
No response
- Dominant language
- TypeScript
- Stars
- 92
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-powerquery-sdk
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/vscode-powerquery-sdk#427 · 1 comment ·
-
microsoft/vscode-powerquery-sdk#419 · 1 assignee ·
-
microsoft/vscode-powerquery-sdk#408 · 1 comment · 1 reaction · 1 assignee ·
-
microsoft/vscode-powerquery-sdk#393 · 1 comment · 1 reaction · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in microsoft/vscode-powerquery-sdk
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·