Automatically generate displayName kewords in TOC files
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- documentation, tooling
Research direction
No source file or test is named. Start by locating the tool that processes toc.yml files and the code that reads linked article F1 metadata. Done means existing displayName keywords are unioned with distinct F1 keywords, while entries without F1 keywords are skipped.
Written by the indexing model from the issue text.
Description
In the sprint meeting today, we discussed a tool that automatically pulls F1 keyword metadata from each linked article in a toc.yml file into the toc.yml file as displayName keywords (used in TOC filtering).
- If there are already displayName keywords, use the union of those and the F1 metadata, and select distinct items.
- If there are no F1 keywords in the linked article, skip that TOC entry.
- Dominant language
- C#
- Stars
- 27
- Forks
- 43
- Avg merge
- 12h 33m
- Merged PRs (30d)
- 26
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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 dotnet/docs-tools
-
[status-checker] Wait 5 minutes before checking for build completionPossibly taken @gewarren claimed this 9 days ago. Open
dotnet/docs-tools#748 · 1 assignee ·
Maintainers usually reply within 1 day
-
Update actions to use commit SHAsPossibly taken @gewarren claimed this 11 days ago. Open:pushpin: seQUESTered
dotnet/docs-tools#743 · 1 assignee ·
Maintainers usually reply within 1 day
-
[Sequester] Improve command line grammarMay be free again @BillWagner claimed this 281 days ago, and no pull request is open. Open:pushpin: seQUESTered
dotnet/docs-tools#611 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
dotnet/docs-tools#572 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dotnet/docs-tools#571 ·
Maintainers usually reply within 1 day
All issues in dotnet/docs-tools
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fluentassertions/fluentassertions#3353 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
unoplatform/uno#24769 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
AvaloniaUI/Avalonia#22323 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microsoft/onnxruntime-genai#2633 ·
Maintainers usually reply within 1 day