Pawl

Bug Fix

- Fix attribute `.current_user_id` on instance `pawl.Linkedin`; it now correctly returns with user's LInkedin ID instead of `None`.

Core Features

- Basic OAuth2 support for `access_token` only.¹
- Access to two Linkedin endpoints (`/me` and `/reactions`).
- `/me`: get your `.basic_profile()` information such as linkedin `id` and other metadata.
- `/reactions`: `.like_post("post_urn")` by `post_urn`.
- Convenience functions in `pawl/utils` to persist your `access_token` in db or in plaintext (don't forget to append to your `.gitignore`).

1) Support for `refresh_token` OAuth2 flow can be provided by way of callback hooks. Please provide feedback if this feature is important to you and how you'd like to use it. Note that Linkedin must grant you permission in order to get access to that particular feature. Since I do not have access to that particular flow, I will rely on your feedback to implement it.

- OAuth2 authentication flow to streamline requests for any Linkedin API services.
- Get your user profile information.

Demo

See [this example](docs/examples/authenticate/01_basic.py) to preview these new features.

Non-production ready release.

- Scaffold package with basic functionality:
- User can obtain basic profile information by invoking `.get_basic_profile()`.