Give everything an object ID #162
Labels
Milestone
Comments
|
should this be using a uuid? if so, does it need to we need to "internalise" the code? |
|
No, a uuid would be overkill. It just has to be unique within the process and predictability is not a concern. Just make it clear in the docs that the ID is easily predictable. It can be made something strong later if we find it's necessary. |
|
having a crack at this.. |
lecstor
added a commit
to lecstor/test-more
that referenced
this issue
Nov 30, 2011
- created a new role HasObjectID using the event_id method from Test::Builder2::Event as method object_id. - added HasObjectID to Event, EventHandler, EventCoordinator, Test::Builder, and Test::Builder2 For Test-More#162
lecstor
added a commit
to lecstor/test-more
that referenced
this issue
Nov 30, 2011
- added object_id docs to consuming classes - created a test for TB2::Formatter testing object_id - added object_id test to History/History.t For Test-More#162
lecstor
added a commit
to lecstor/test-more
that referenced
this issue
Nov 30, 2011
- added object_id docs to consuming classes that missd out last time. - gave TestState it's own object_id For Test-More#162
|
@lecstor Cool, that'll do it. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It will be very useful for everything to have an object ID.
Extract
event_idfrom Test::Builder2::Event, turn it into a role, call the new attributeobject_idand add it to Event, EventWatcher, EventCoordinator, Test::Builder and Test::Builder2.The text was updated successfully, but these errors were encountered: