Maf Obsolete Api Registry

Obsolete API Registry

This registry is the source of truth for all known [Obsolete] APIs in MAF 1.3.0.

How to Use This Skill

1. A cs0618-hunter scan has produced one or more CS0618 warning lines
2. Extract the obsolete method name from the warning text
3. Look it up in registry.yaml (in this directory)
4. Apply the replacement_pattern exactly as documented
5. If the warning is NOT in the registry — add it (see "Adding New Entries" below)

registry.yaml Format

- id: 
  package: 
  version_introduced: 
  type: 
  method: 
  obsolete_signature: 
  replacement_signature: 
  argument_order_change: 
  fix_description: 
  example_before: |
    
  example_after: |
    
  cs_warning: CS0618
  guide_section: 
  notes: 

Adding New Entries

When cs0618-hunter finds a CS0618 warning that is NOT in registry.yaml:

1. Open registry.yaml
2. Add a new entry using the format above
3. Fill in the obsolete and replacement signatures from the compiler warning message
4. Test the fix — confirm the warning disappears after applying it
5. Commit the updated registry.yaml alongside your migration changes

This is how the registry grows over time — each migration run that finds a new obsolete API enriches the registry for future runs.

---

Current Registry Contents

See registry.yaml for the full machine-readable data. Current entries:

| ID | Method | Obsolete signature | Replacement | |----|--------|--------------------|-------------| | MAF130-FAN-IN-001 | WorkflowBuilder.AddFanInBarrierEdge | (ExecutorBinding target, IEnumerable sources) | (IEnumerable sources, ExecutorBinding target) |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: joslat
• Source: joslat/maf-doctor
• License: MIT

Install and usage instructions live in the source repository linked above.