Open jasonchoimtt opened 9 years ago
The current code does not correctly resolve the id from the intended order: attribute -> key, but instead will raise an AttributeError if there is no such attribute. It will also not accept a falsy .id attribute, e.g. 0. This patch fixes the issue.
This is addressed in #63 as well.
The current code does not correctly resolve the id from the intended order: attribute -> key, but instead will raise an AttributeError if there is no such attribute. It will also not accept a falsy .id attribute, e.g. 0. This patch fixes the issue.