Skip to content
This repository has been archived by the owner on Nov 14, 2019. It is now read-only.

Handle null fields when summarizing #73

Open
stvnrlly opened this issue May 17, 2016 · 2 comments
Open

Handle null fields when summarizing #73

stvnrlly opened this issue May 17, 2016 · 2 comments

Comments

@stvnrlly
Copy link
Member

Currently, the bot assumes that common fields will always be available for parsing, but that's not the case. Instead, the bot should ignore the field if it's null.

@mgwalker
Copy link
Member

mgwalker commented Jan 3, 2017

Do you have any more info on this one? I'm not sure what it's referring to and can only find one place where null kind of misbehaves. I'm guessing this got fixed incidentally when you did all the work on the interview.

@stvnrlly
Copy link
Member Author

stvnrlly commented Jan 3, 2017

It might have been mostly fixed, but I did see this today. My previous standup was a simple "OOO" one, and the previous blocker was listed as null. That might be the sole remaining thing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants