Fix authorization token configuration in README

[fnaisua]

READ AND DELETE THIS SECTION BEFORE SUBMITTING PR

• Fill out each REQUIRED section
• Fill out OPTIONAL sections, remove section if it doesn't apply to your PR
• Read and fill out each of the checklists below
• Remove this section after reading

Description

One Line Summary

REQUIRED - Very short description that summaries the changes in this PR.

Details

Motivation

REQUIRED - Why is this code change being made? Or what is the goal of this PR? Examples: Fixes a specific bug, provides additional logging to debug future issues, feature to allow X.

Scope

RECOMMEND - OPTIONAL - What is intended to be effected. What is known not to change. Example: Notifications are grouped when parameter X is set, not enabled by default.

OPTIONAL - Other

OPTIONAL - Feel free to add any other sections or sub-sections that can explain your PR better.

Testing

Manual testing

REQUIRED - Explain what scenarios were tested and the environment.

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
  • If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
  • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
• I have reviewed this PR myself, ensuring it meets each checklist item
  • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

[sherwinski]

Hey @fnaisua,

setAppKeyToken was changed to setRestApiKeyToken in the latest major version (v5). Can you confirm what version you are using in your project?

[serhii-petrov-betterme]

@sherwinski latest major version (v5) is in beta, so when installing package via composer by default it'll install v2.2

so for most users who just run composer require onesignal/onesignal-php-api v2.2 will be installed and therefore mentioning setRestApiKeyToken in the README is irrelevant for them.

I run into by myself thinking that doc might be outdated, then eventually I realized I'm on "older" but stable version

Are you going to release v5 version as stable version anytime soon?

[sherwinski]

Hey @serhii-petrov-betterme, we're happy to share that we published the first stable v5 release (https://github.com/OneSignal/onesignal-php-api/releases/tag/v5.3.0) yesterday. Therefore, users should be pulling in the latest version by default from now on.

Appreciate everyone's patience as we worked to get to this point. I'm going to close this now as the docs should match the expected user experience.