Skip empty records in map

[jheddings]

I'm not sure if this is the best way to handle the error, but this seems to work around the problem I've been having today.

Workaround for #269

[julrach]

heard that this was a fix to the #269 error so just thought i'd +1 this right here

[jheddings]

There appears to be a field (__json__) in the user content that is occasionally set to None. This simply does a quick check and skips adding any empty record sets to the store.

[AndreClaassen1]

Thank you for your work. But still, I'm uneasy as to why this is occurring right now or this is the prelude to major API changes.

[ttran]

Ha! This broke everything all at once for us 💯

[jheddings]

Are you referring to the change in this pull request or the bug?

[ttran]

Are you referring to the change in this pull request or the bug?

The bug! Thank you for the fix :)

[jheddings]

Sure thing... It was a quick change, just making sure it didn't have some other consequences 😄

[ttran]

For folks wanting to monkey patch their code while waiting on the merge:

import notion
def store_recordmap(self, recordmap):
    for table, records in recordmap.items():
        if records is None: continue
        for id, record in records.items():
            self._update_record(
                table, id, value=record.get("value"), role=record.get("role")
            )
notion.store.RecordStore.store_recordmap = store_recordmap

[phouse512]

I had to modify the first line in the above snippet to be import notion.store instead of import notion for it to work for me with python3.6 and notion==0.0.27.

thank you for the workaround until this gets merged!

[jamalex]

Thanks for the prompt fix on this, @jheddings! Appreciate the contribution. I'll be cutting a new release tonight with this in it.