Issues with _types

[jbesomi]

• Fix type checks to not fail if first value in series is NaN/missing, see Fix type checks to not fail if first value in series is NaN/missing. #174
• We don't need anymore to check for RepresentationSeries
• Then we might not need to check for the number of levels .. or s.index.nlevels != 1? Or if we do we should have a separate warning message "number of level is too high ..."
• At line 163 of _types is written: "Check if a given Pandas Series has the properties of a RepresentationSeries.". Shouldn't we check for VectorSeries instead?
• Some new representation functions might accept as input both a DataFrame and a VectorSeries. Does InputSeries deal with that? Do we need a more general approach?

[henrifroese]

Checklist for the items:

• Fix type checks to not fail if first value in series is NaN/missing, see Fix type checks to not fail if first value in series is NaN/missing. #174
• We don't need anymore to check for RepresentationSeries -> this will be solved in HeroTypes in Representation; DataFrame in _types #157
• Then we might not need to check for the number of levels .. or s.index.nlevels != 1? Or if we do we should have a separate warning message "number of level is too high ..." -> this will be solved in HeroTypes in Representation; DataFrame in _types #157
• At line 163 of _types is written: "Check if a given Pandas Series has the properties of a RepresentationSeries.". Shouldn't we check for VectorSeries instead? -> already solved in master through Change representation_series to DataFrame #156
• Some new representation functions might accept as input both a DataFrame and a VectorSeries. Does InputSeries deal with that? Do we need a more general approach? -> Yes! HeroTypes in Representation; DataFrame in _types #157 adds support for several input types 🥳

[henrifroese]

Will leave this open until #157 is merged as we might encounter some more issues etc. 🤷 🤷‍♂️ 🤷‍♀️

[henrifroese]

Can be closed as #157 is merged, see comment above.