[NEWS] Evolute to 4. Beta version in Pypi

What's Changed

• chore: Update Notebook by @IvanildoBarauna in #45
• feat Improves by @IvanildoBarauna in #47

Full Changelog: 1.2.1...1.2.3

Update Documentation and Improve Dev XP

• Rename param delay to intial_delay
• Refact tests

Retry Strategies Avaliable

A new version 1.2.1 of api-to-dataframe is LIVE
We are happy to announce another version of the solution you need to be more productive in your developments that involves API consumption to generate DataFrames.

Now Scientists, Data Engineers, Data Analysts and all other professionals who need to obtain API data and create dataframes can use RETRY STRATEGIES.

Retry Strategies is a feature that allows you to define a Retry strategy in case your GET operation fails. We don't want that to happen, but if it does, we're here to try again in a safe way.

There are two ways to do this, you can use a Linear Strategy which by default makes 3 retries, waiting 1 second each time, or use an Exponential Strategy which doubles the waiting time with each new connection attempt, to protect the servers from APIs you consume. It is worth remembering that all parameters have default values, but can be changed according to your needs.

We hope you enjoy this new feature,

In addition, we have evolved the package to version 3. Alpha, we are one step away from evolving into a beta version, so any feedback/questions are welcome here.
For details on how to implement your Retry strategies, access our README and also this notebook which contains examples of how to do this in a simple way.

Kind Regards,
Ivanildo Barauna

✅ Implemented RetryStrategies

A new version 1.2.0 of api-to-dataframe is LIVE

We are happy to announce another version of the solution you need to be more productive in your developments that involves API consumption to generate DataFrames.

Now Scientists, Data Engineers, Data Analysts and all other professionals who need to obtain API data and create dataframes can use RETRY STRATEGIES.

Retry Strategies is a feature that allows you to define a Retry strategy in case your GET operation fails. We don't want that to happen, but if it does, we're here to try again in a safe way.

There are two ways to do this, you can use a Linear Strategy which by default makes 3 retries, waiting 1 second each time, or use an Exponential Strategy which doubles the waiting time with each new connection attempt, to protect the servers from APIs you consume. It is worth remembering that all parameters have default values, but can be changed according to your needs.

We hope you enjoy this new feature,

• In addition, we have evolved the package to version 3. Alpha, we are one step away from evolving into a beta version, so any feedback/questions are welcome here.

For details on how to implement your Retry strategies, access our README and also this notebook which contains examples of how to do this in a simple way.

Kind Regards,
Ivanildo Barauna

Timeout, Headers and Increase CodeCov

**Whats the new:

• Added timeout parameter
• Added header parameter
• Increase CodeCoverage > 95%
• Update Documentation

Full Changelog: 1.0.3...1.1.0

💻 Improved Development Experience

** Whats has changed?

• Remove unecessary packages on import moment for better development experience
• Update your library and enjoy

Thanks
Ivanildo Barauna

📰 Improved Documentation

What's Changed

• FEATURE: DocsStrings in all methods for better development experience
• FEATURE: Update Readme with Installation and Code User Guide
• FEATURE: Remove unecessary methods on import lib

Full Changelog: 1.0.1...1.0.2

HOTFIX Version of Dependencies

What's Changed

• feat: change entrypoint of lib + split responsabilites in components by @IvanildoBarauna in #29

Full Changelog: 1.0.0...1.0.1

1.0.0

Full Changelog: 0.1.0...1.0.0

0.1.0

• Added entrypoint
• Writed unitest (CodeCov - 97%)
• Implement the firsts methods for use