Add `rootPath` handling in useSession

[brunorodmoreira]

What problem is this solving?

Sessions APIs request didn't consider the rootPath when building the URL, then the requests return an error 404.

How to test it?

It should be tested in public domains because there's no rootPath in "myvtex", it's a CDN routing thing. I created two workspaces with Store Theme to ease the visualization.

With my improvement Without my improvement

The page should be scrolled to the first shelf because there are other Sessions requests from another component.

Screenshots or example usage:

• Improved

• Not improved

• Ensure the caller

Describe alternatives you've considered, if any.

Related to / Depends on

How does this PR make you feel? :link:

![](put .gif link here - can be found under "advanced" on giphy)

[vtex-io-ci-cd[bot]]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• [x] Patch (backwards-compatible bug fixes)

• [ ] Minor (backwards-compatible functionality)

• [ ] Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• [ ] No thanks, I would rather do it manually 😞

[filipewl]

About the checks:

• PR actions / IO app test (pull_request) has failed to execute successfully, but not for reasons from this PR. Seems related to this issue https://github.com/vtex-apps/store-discussion/issues/705. I've run the tests locally and they're all passing.
• PR actions / Lint (pull_request) also failed to execute for the same reason above. But it was already failing, as can be seen in the last merged PR, so nothing from here.
• vtex-io/docs-outdated-select, for some reason the bot didn't left the comment where we can select the checkbox for the documentation. But there isn't anything to document here, so we're fine.

---

With all that said, I'm going ahead to merge and deploy this.

[vtex-io-ci-cd[bot]]

Your PR has been merged! App is being published. :rocket: Version 2.83.1 → 2.83.2

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy vtex.product-summary@2.83.2

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. :book: