Comment #3 on issue 1628 by [email protected]: Remote interface does not support reporting continuable and fatal errors
http://code.google.com/p/robotframework/issues/detail?id=1628

When reading comment 2 before getting to the end, I felt separate boolean keys didn't seem like a good approach and a single key to define status was better. But I guess both approaches have their pros & cons.

I would prefer being explicit/specific or granular on naming the special case statuses, as their would be less uncertainty on what they actually define.

Another thought on the single key approach, what if we made the single new key instead of be a simple string key value pair, make it a dictionary that contains a possible list of values (empty, 1, or more). The overall result dictionary would then be a bit more complex containing one key that is a dictionary with more subkeys. But this approach would mean the result dictionary doesn't grow with more special case keys, as those cases are instead nested under the the new 'error-type' key.

Unless there seems to be considerable complexity this way, I'd prefer new key support multiple values by being a dictionary. I think this would offer flexibility and support case of the special cases being combinable and when they're not.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--

--- You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to