doctrine/archived-orm
1
0
Fork 0
mirror of https://github.com/doctrine/orm.git synced 2026-03-24 06:52:09 +01:00
Code Issues 5.3k Packages Projects Releases 100 Wiki Activity

query parameters mapping : make better error message #4973

New Issue
Open
opened 2026-01-22 14:54:49 +01:00 by admin · 2 comments
admin commented 2026-01-22 14:54:49 +01:00
Owner
Copy Link

Originally created by @kcassam on GitHub (Jan 13, 2016).

196ea2d0c5/lib/Doctrine/ORM/Query.php (L306-L313)

Observed : Today, error messages states too many parameters or to few parameters, we only have a count, but it can be difficult to track what's wrong

Expected : It would be developer friendly to list the parameters and the mappings

Originally created by @kcassam on GitHub (Jan 13, 2016). https://github.com/doctrine/doctrine2/blob/196ea2d0c512dda56ebcbdf7a1535d20cbc2ad43/lib/Doctrine/ORM/Query.php#L306-L313 Observed : Today, error messages states too many parameters or to few parameters, we only have a count, but it can be difficult to track what's wrong Expected : It would be developer friendly to list the parameters and the mappings
admin added the Improvement label 2026-01-22 14:54:49 +01:00
admin commented 2026-01-22 14:54:49 +01:00
Author
Owner
Copy Link

@svencan commented on GitHub (Feb 10, 2017):

I would like to look into this, although I'm new to FOSS contribution.

Do we want a complete list of parameters and mappings in the exception, or first-failed-mapping indication so that developers can fix wrong mappings one by one?

@svencan commented on GitHub (Feb 10, 2017): I would like to look into this, although I'm new to FOSS contribution. Do we want a complete list of parameters and mappings in the exception, or first-failed-mapping indication so that developers can fix wrong mappings one by one?
admin commented 2026-01-22 14:54:50 +01:00
Author
Owner
Copy Link

@Ocramius commented on GitHub (Feb 10, 2017):

@svencan I'd start from suggesting an example error message that is more friendly (just write it here as a start).

Then we just add it to a test and continue from there 👍

@Ocramius commented on GitHub (Feb 10, 2017): @svencan I'd start from suggesting an example error message that is more friendly (just write it here as a start). Then we just add it to a test and continue from there 👍
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BC Break
Bug
Can't Fix
Deprecation
Documentation
DQL
Duplicate
Failing Test
Hacktoberfest
Improvement
Improvement
Incomplete
Invalid
Missing Tests
New Feature
PR Created
pull-request
Mirrored from GitHub Pull Request
 Question
Regression
Status: Waiting feedback
Waiting feedback
WIP
Won't Fix
No Label Improvement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#4973
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?