Closed ismell closed 6 years ago
Beyond failing specs / merge conflicts, is there anything preventing this from being merged? I've run into a situation where this has caused a problem. (I would probably also recommend pulling the logic around the InResponseTo
out of the long assertion
/ xml
strings.)
Tagging @lawrencepit (since I'm not sure if GitHub would send a notification otherwise)
Just saw that the commit got pulled into 0.3.4, thanks!
TheInResponseTo is optional. If it's not specified we should not render it because it will fail schema validation.