-
Notifications
You must be signed in to change notification settings - Fork 14
Open
2 / 42 of 4 issues completedDescription
I opened this issue to track all the steps we need to reach the release of V3:
- Move all the duplicated logic in common function: Thanks to the initial implementation of the async version Add async support #72 of the package, we have a lot of duplicated code. To make future maintenance easier, I want to place all the code into a common function;
- Enable configuration options for the HTTP client: The idea is mentioned on Add async support #72 (comment). I would like to avoid introducing a new flag for each HTTP client configuration, as we did for proxy Add support for proxy #17, SSL Add ssl verify flag #70, and timeout Add async support #72.
- Introduce a logger: A few people have provided code examples for most GitHub issues. I want to implement a logger to help gather useful information for debugging issues.
- Fix the tests: Following Add async support #72, all the tests are failing. We need to fix them;
- Upgrade the linter to V7.3: We paused linter upgrades after Cannot update super linter due to failed checks #48 due to instability and some breaking changes. Since Add async support #72 is a breaking change, we will take this opportunity to update the linter since V7.3 is stable;
- Create GitHub pages: I want to publish the package documentation using pdoc as GitHub pages for the project
- Create
CONTRIBUTING.md
- Update
README.md
- Write a migration guide from V2 to V3
- (Optional) Create a legacy client: create a client that uses requests, like we did in V2, for backward compatibility with the package.
- (Optional) Rename the project: This project began by scraping the site; it is now more of an API Wrapper. Should we change its name to avoid confusion?
- Cookie configuration: Add the possibility of choosing the cookie name to fetch. As suggested in 403 status code discussion #59 (comment)
- Reach 100% coverage
Sub-issues
Metadata
Metadata
Assignees
Labels
No labels