Recommended values do not allow None values as input

[KarolisCremers]

To enable **Kwarg like behaviour we could make it so that the recommended properties in the sempyro classes accept None as a valid input. As the default value for recommended properties is None already, this would not change behaviour, but would improve QOL when dealing with data streams where recommended properties are not always in the resources descriptions.

Alternative question:
Is this the desired behaviour for recommended properties?

[agjharms]

Hi Karolis,

Thank you for bringing this to our attention. After looking into it, I found that in order to provide 'None' as a value, the type of the property should be wrapped in a Optional[] statement. To process this change the type hints for all recommend properties should be changed, which will take some time.

I don't quite understand your alternative question. Could you clarify which behaviour your referring to?