Create migration guide from v2 to v3#1630
Merged
henriquemoody merged 1 commit intoRespect:mainfrom Jan 27, 2026
Merged
Conversation
henriquemoody
force-pushed
the
migrating-from-v2-to-v3
branch
from
f83b850 to
1cd1507
Compare
There was a problem hiding this comment.
Pull request overview
This PR adds a comprehensive migration guide to help users transition from Respect\Validation v2.x to v3.0. The document covers breaking changes, new features, and provides detailed examples for updating code.
Changes:
- Added a new migration guide document (
docs/migrating-from-v2-to-v3.md) that covers all breaking changes and new features in version 3.0 - Includes detailed code examples showing before/after comparisons for migrating from v2.x to v3.0
- Provides a quick reference section for common migration patterns
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
henriquemoody
force-pushed
the
migrating-from-v2-to-v3
branch
3 times, most recently
from
977aecc to
eddb8ee
Compare
henriquemoody
commented
Jan 27, 2026
| **After (3.0):** Single file with `#[Template]` attribute: | ||
|
|
||
| ```php | ||
| use Respect\Validation\Message\Template; |
Member
Author
There was a problem hiding this comment.
Shall we just move this to the Respect\Validation namespace?
henriquemoody
force-pushed
the
migrating-from-v2-to-v3
branch
5 times, most recently
from
25eb2c0 to
25d5694
Compare
As we approach the release of version 3.0, it is important to provide our users with a clear guide to migrating from version 2.x to 3.0. This commit provides guidance by creating a document that will remain in the repository, so users can always access it.
henriquemoody
force-pushed
the
migrating-from-v2-to-v3
branch
from
25d5694 to
68ed5d2
Compare
alganet
reviewed
Jan 27, 2026
alganet
approved these changes
Jan 27, 2026
Member
alganet
left a comment
alganet
left a comment
There was a problem hiding this comment.
Let's merge this as it is and improve anything in further PRs. I think it's currently great, and there's no reason to delay making it into the repo.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As we approach the release of version 3.0, it is important to provide our users with a clear guide to migrating from version 2.x to 3.0. This commit provides guidance by creating a document that will remain in the repository, so users can always access it.