[SDK-3547] Rename client_id to clientId

[ewanharris]

Changes

Renames client_id on the public API to clientId for consistency with the JS ecosystems preference for camelCase, whilst maintaining sending client_id back to Auth0 in requests.

For consistencies sake within the codebase, except for CacheEntry the cache related code was also updated to use clientId over client_id. CacheEntry was not migrated to not break existing cached data

This will require users of this package to rename the property on their side. The diff for this looks like as follows

• Auth0Client constructor

const auth0 = new Auth0Client({
  domain: '<AUTH0_DOMAIN>',
- client_id: '<AUTH0_CLIENT_ID>'
+ clientId: '<AUTH0_CLIENT_ID>'
});

• createAuth0Client helper

const auth0 = await createAuth0Client({
  domain: '<AUTH0_DOMAIN>',
- client_id: '<AUTH0_CLIENT_ID>'
+ clientId: '<AUTH0_CLIENT_ID>'
});

This change also applies to the buildLogoutUrl and logout methods on Auth0Client.

However, if you are implementing a custom cache the CacheEntry structure still maintains the snakecase client_id for backwards compatibility with existing cached data so there is no migration needed for custom cache implementations.

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All code quality tools/guidelines have been run/followed

[frederikprijck]

This will put clientId in our cache, while previously it was client_id, this would make old cached values return undefined for clientId and breaking it for our users. Even though with a new major we can add breaking changes, we should try and avoid breaking it for the end-user (try and avoid logging users out with our breaking changes)

I think we should be able to either:

• As the cache is also using snake_case, keep the client_id in CacheEntry to be snake_case
• Keep it camelCased, but ensure it gets mapped to snake_case again before putting in cache. If we would do that, I think we should also camelCase all other properties on the cacheEntry.

[ewanharris]

As discussed, moved the cache back to using client_id