Skip to content

Add AppSource lifecycle knowledge + a unified analyzer/compiler rule index #36

Description

@JesperSchulz

Context

The README lists "AppSource lifecycle" in scope; nothing exists yet. AppSourceCop (distinct from CodeCop) is the textbook case for this repo's admission test — rule-numbered guidance an LLM cannot reproduce from memory.

Why it matters (admission test)

AppSourceCop rules, technical-validation requirements, and the AppSource breaking-change policy differ from on-prem and are routinely violated by generated code. Encoding the rule numbers + fixes is exactly what BCQuality is for.

Scope / checklist

AppSource lifecycle (microsoft/knowledge/appsource/)

  • AppSourceCop AS0xxx rules — mandatory affix/prefix, missing permission set, breaking changes vs. baseline, on-prem-only APIs in a cloud target, help links.
  • app.json AppSource requirements — brief, description, logo, privacy statement, EULA, help/url, contextSensitiveHelpUrl, propagateDependencies, target.
  • PerTenantExtensionCop where it diverges.
  • Partner Center submission & validation gotchas.

Unified analyzer/compiler rule index (cross-cutting; lives here because AppSourceCop is the exemplar)

  • A reference mapping CodeCop (AA0xxx), UICop (AW0xxx), AppSourceCop (AS0xxx), PerTenantExtensionCop (PTE0xxx) and key compiler diagnostics (AL0xxx) → cause + fix, so review findings can cite rule numbers and generators can pre-empt them.

Each new knowledge file must pass the README admission test and the CI-validated frontmatter schema.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions