Sheetwork

================================================================

Features
--------

- `337 <https://github.com/bastienboutonnet/sheetwork/issues/337>`_: "Yes" and "No" strings will now get mapped to ``True`` and ``False`` if a user asks for a column with such content to be cast to boolean.

===========================================================

Bug Fixes
---------

- `323 <https://github.com/bastienboutonnet/sheetwork/issues/323>`_: Columns to be converted to booleans which contained empty strings were converted as ``np.nan`` after sheet ingestion. Because this value had not been added to the allowable values for boolean conversion, users who had null values in their sheets could have ran into the app raising an error and not wanting to convert. Given that it is perfectly fine to have ``null`` values among booleans it is now made possible.

===================================================

Bug Fixes
---------

- `320 <https://github.com/bastienboutonnet/sheetwork/issues/320>`_: ``--version`` was broken because of a bad indentation choice. It is now fixed. This PR also removed some ugly left over prints. Apologies about this 🤦

=============================

Under The Hood/Misc
-------------------

- `295 <https://github.com/bastienboutonnet/sheetwork/issues/295>`_: ``make_df_from_worksheet()`` now throws more errors and wraps them into the a custom exception named ``SheetLoadingError``. The previous behaviour was causing too much silentness and prevented user from seeing errors such as the ones highlighted in `#292 <https://github.com/bastienboutonnet/sheetwork/issues/292>`_


- `304 <https://github.com/bastienboutonnet/sheetwork/issues/304>`_: Empty headers are a pain, but not uncommon. More often than not, users have their google sheet start on the second or so row. This causes all sorts of unexpected behaviour when we're trying to land the table into the database as we don't know what column names to give.

This PR implements a check of whether the header contains empty column names and alerts raises an error asking the user to fix the GoogleSheet from the source.

In the next feature release (v1.1.0) we will allow users to specify the index of the header so that they do not have to change it in the source in case that is not an option or so.

**Contributed by:** `jflairie <https://github.com/jflairie>`_

===============================================================================

Bug Fixes
---------

- `290 <https://github.com/bastienboutonnet/sheetwork/issues/290>`_: Boolean data-type casting was buggy somewhere between ``v1.0.0`` and ``v1.0.2`` and resulted to all non null strings to be given a ``True`` value. We now handle boolean conversion explicitly by mapping strings ``false`` and ``true`` to python ``False`` and ``True`` that pandas can actually understand and expose to the database appropriately. **NOTE**: If the user asks for a column to be cast to boolean but this column contains any other string than the aforementioned ones (and capitalised
variants) ``sheetwork`` will throw a ``ColumnNotBooleanCompatibleError`` that will help the user locate the offending column as well as the offending value(s).

=========================================================

Features
--------

- `282 <https://github.com/bastienboutonnet/sheetwork/issues/282>`_: Sheetwork now retries obtaining google sheets up to 3 times (max duration 10s) if it hits an ``APIError`` because the end-user or service account was rate limited or other common service availability errors encountered by end users.

Check the PR to see the exact set of ``APIError`` that sheetwork will attempt retrying for.