fix: update API endpoint

[aversini]

Summary by CodeRabbit

• Chores
  • Updated production API endpoint to "https://mylogin.gizmette.com" for improved reliability.

[coderabbitai]

Walkthrough

The change updates the production API endpoint for the authentication provider module. The old endpoint "https://auth.gizmette.com" is replaced by "https://mylogin.gizmette.com" to reflect the updated service URL.

Changes

Files	Change Summary
packages/auth-provider/src/…/constants.ts	Updated the prod API endpoint URL from "https://auth.gizmette.com" to "https://mylogin.gizmette.com".

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Bundle Size

Status	File	Size (Gzip)	Limits
✅	index.js	2.59 KB (+105 B +4.11%)	3 kb

Overall bundle size: 2.59 KB (+105 B +4.11%)
Overall status: ✅

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3dbd373 and 357a1f6.

Files selected for processing (1)

• packages/auth-provider/src/common/constants.ts (1 hunks)

Additional comments not posted (1)

packages/auth-provider/src/common/constants.ts (1)

8-8: Update to production API endpoint verified.

Verification successful

The new API endpoint is present in the packages/auth-provider/src/common/constants.ts file. However, we need to ensure that the old endpoint is not present anywhere in the codebase.

---

The absence of output from the search for the old API endpoint suggests that it is not present in the codebase. Given that the new endpoint is found in the expected file, we can confirm that the update has been made correctly.

• packages/auth-provider/src/common/constants.ts: The new endpoint https://mylogin.gizmette.com is present.

Scripts executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Description: Verify the new API endpoint is used consistently across the application.

# Test: Search for the old and new API endpoint usage. Expect: No occurrences of the old endpoint.
rg --type ts $'https://auth.gizmette.com' && rg --type ts $'https://mylogin.gizmette.com'

Length of output: 40

---

---

Script:

#!/bin/bash
# Description: Verify the new API endpoint is used consistently across the application.

# Test: Search for the new API endpoint usage. Expect: Occurrences of the new endpoint.
rg --type ts 'https://mylogin.gizmette.com'

Length of output: 129

---

---

Script:

#!/bin/bash
# Description: Verify the old API endpoint is not used anywhere in the application.

# Test: Search for the old API endpoint usage. Expect: No occurrences of the old endpoint.
rg --type ts 'https://auth.gizmette.com'

Length of output: 40