Validate against duplicate or otherwise corrupt content

Open
#79 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
documentation, tooling

Research direction

The issue does not name any files, tests, or entry points. Start by locating the tool's content-processing and command-line mode handling, then determine how duplicate or corrupt content is currently handled. Done means a validate mode reports these conditions and the behavior for invalid content is defined.

Written by the indexing model from the issue text.

Description

port-to-docs

A lurking bug for sure, but one that would likely cause issues for us elsewhere too. The docs site would probably struggle if duplicates existed. We could benefit from a "validate" mode in this tool that would report on any such issues; we could then define the behavior for invalid content.

Originally posted by @jeffhandley in https://github.com/carlossanlop/DocsPortingTool/pull/77#discussion_r681089559

Dominant language
C#
Stars
14
Forks
21
No merged PRs in 30d

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.

More from dotnet/api-docs-sync

All issues in dotnet/api-docs-sync

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.