Developer gaps: AotCheck needs vswhere on PATH; Pandoc tests skip silently locally

Open Beginner friendly
#164 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp

Research direction

Start by reading README, AGENTS.md, run.ps1, and PandocAgreementTests to see how the AotCheck publish command and local test skips are handled. Check the repository’s CI setup for the expected pandoc behavior. Done when the Visual Studio Installer path requirement is documented or configured, and missing pandoc produces a visible skip reason or is required locally.

Written by the indexing model from the issue text.

Description

  1. dotnet publish tests/AotCheck -r win-x64 fails at the native link step unless C:\Program Files (x86)\Microsoft Visual Studio\Installer is on PATH. Document this in README/AGENTS.md or set it in run.ps1. 2. PandocAgreementTests skip without a message when pandoc is missing and CI isn't set. Make the skip visible (a skip reason that names pandoc) or require pandoc locally. Found by the checker inventory (2026-11-06).
Dominant language
C#
Stars
0
Forks
0
Avg merge
1h 43m
Merged PRs (30d)
43

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from sillsdev/SIL.TextEditing

All issues in sillsdev/SIL.TextEditing

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.