Skip to content

🚀 Feature: change validate to return rich Result type #754

Description

@michaelfaith

Feature Request Checklist

Overview

This is the umbrella issue tracking the rollout of the change to validate's return type, to include the rich Result type, instead of just error messages for each top-level property. We'll do it in two phases:

  1. Introduce the new return type as opt-in via optional parameter (Non-Breaking)
  2. Change return type to be the new type and remove the optional param (Breaking)

Additional Info

Question: is this overkill? Should we just collapse 2 and 3 into one band-aid rip after enough time has passed with the opt-in behavior? cc @JoshuaKGoldberg thoughts? Updated to just be one breaking change

Metadata

Metadata

Assignees

Labels

status: trackingThe issue is just for tracking, and not directly actionable.type: featureNew enhancement or request 🚀

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions