Skip to content
This repository has been archived by the owner on Jul 8, 2023. It is now read-only.

Attempting to mock a non-existant class gives a vague error message. #40

Closed
jmalloc opened this issue Oct 23, 2014 · 2 comments
Closed

Attempting to mock a non-existant class gives a vague error message. #40

jmalloc opened this issue Oct 23, 2014 · 2 comments
Labels
enhancement
Milestone
0.1.1

Comments

@jmalloc
Copy link
Member

jmalloc commented Oct 23, 2014

eg:

Eloquent\Phony\Mock\Exception\InvalidTypeException: Unable to add type of type 'string'.

It would be great if the value passed (ie the string that is "just a string" and not a valid class name) was included in the error message.
@jmalloc
Copy link
Member Author

jmalloc commented Oct 23, 2014

FYI @koden-km

@ezzatron ezzatron added this to the 0.2.0 milestone Oct 23, 2014
@ezzatron
Copy link
Contributor

Fixed in 0.1.1.

@ezzatron ezzatron modified the milestones: 0.2.0, 0.1.1 Nov 18, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
0.1.1
Development

No branches or pull requests
2 participants
@ezzatron @jmalloc