The new handling of potential None values for "name" and "surname" isn't covered by tests. Given this was fixing a production AttributeError, it would be good to add unit tests in TestAuthor that explicitly cover cases where these keys are present but set to None, to prevent regressions in the OpenAIRE parsing path.
Originally posted by @Copilot in #47 (comment)
The new handling of potential
Nonevalues for"name"and"surname"isn't covered by tests. Given this was fixing a productionAttributeError, it would be good to add unit tests inTestAuthorthat explicitly cover cases where these keys are present but set toNone, to prevent regressions in the OpenAIRE parsing path.Originally posted by @Copilot in #47 (comment)