Change logic to preserve token

[marcospassos]

Summary

Here’s an improved version of your description:

Before this PR, passing userId as null would clear the token, even if the current token was anonymous. This caused issues for organizations with multiple applications, where some use signed tokens and others do not. For those not using signed tokens, passing null would generate an unsigned token, which lacks a token ID and initiates a new session.

With this update, the token is only regenerated if the subject changes. To retain the previous behavior, use token: null instead.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/@croct/sdk@433

commit: 5233dd8

[codeclimate]

Code Climate has analyzed commit 5233dd8 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 99.9% (0.0% change).

View more on Code Climate.