configurable date format and handle decimal InvalidOperation

[aroder]

• Adds a property date_format that makes the target key's date format configurable. It defaults to the original hard-coded date format, making this change backwards compatible.
• Adds a line to adjust the decimal precision if it is too small compared to the tap's schema

@ome9ax are you open to a PR for this, or open to discuss?

[aroder]

Hi @ome9ax bumping this. Do you have time to review?

[ome9ax]

Thanks for your contribution @aroder
Left a note, Let me know your thoughts.

[ome9ax]

Those are already in the [options.extras_require] section L34-35. I keep them apart as they are not needed to run the package, only to run the tests.
My rational is to keep the target lean if possible.

So I don't know how much of a best practice it is but I used

pip install --upgrade .[test,lint,dist]

To install what's needed on local. It was my way of following the KISS principle here.

[ome9ax]

That a great one. Thanks for adding it.

[ome9ax]

Reading the Handle multipleOf overflow fix introduced in jsonschema v4.0.0, I wonder if that update doesn't make adjust_precision_for_schema reduntant?

[haleemur]

I would like to note that the current implementation allows for specifying the date format already. the additional parameter might be redundant.

e.g.

naming_convention: "{stream}/export_date={date:%Y-%m-%d}/{timestamp}-{stream}.json"

however, we should add some parsing logic to ensure that the naming convention provided is valid and update the documentation with some examples.

[ome9ax]

adjust-precision-for-schema merged in #75 and available in the v1.2.2 release @aroder .
Also closes #69 .
I believe this PR can now be closed unless reasons not to.

[ome9ax]

All the functionalities are now implemented.