This PR replaces the current offering's actual code around OAuth (creating the redirection URL and validating the callback) with the new library, but preserves the client-facing side of things, such as making sure we have cookie access, top level redirections, etc.
It also now logs in as an embedded app, which will start using JWT by default.
WHAT is this pull request doing?
Including the new library and using its OAuth functions, and setting up so JWT sessions can be used.
These changes are actually NOT a major changes by themselves - the external API has not changed at all, but apps using it will need to call Shopify.Context.initialize and start using App Bridge's authenticatedFetch.
Type of change
[ ] Patch: Bug (non-breaking change which fixes an issue)
[ ] Minor: New feature (non-breaking change which adds functionality)
[X] Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist
[x] I have added a changelog entry, prefixed by the type of change noted above
WHY are these changes introduced?
This PR replaces the current offering's actual code around OAuth (creating the redirection URL and validating the callback) with the new library, but preserves the client-facing side of things, such as making sure we have cookie access, top level redirections, etc.
It also now logs in as an embedded app, which will start using JWT by default.
WHAT is this pull request doing?
Including the new library and using its OAuth functions, and setting up so JWT sessions can be used.
These changes are actually NOT a major changes by themselves - the external API has not changed at all, but apps using it will need to call
Shopify.Context.initializeand start using App Bridge'sauthenticatedFetch.Type of change
Checklist