Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Angular] Remove unnecessary PROXY_HOST setting #2036

Merged
merged 4 commits into from
Feb 7, 2025
Merged

Conversation

illiakovalenko
Copy link
Contributor

@illiakovalenko illiakovalenko commented Feb 7, 2025

Description / Motivation

The PROXY_HOST setting was initially introduced to construct the target request URL, as all requests are routed through a proxy during client-side navigation. However, further investigation has shown that this setting is no longer needed. The request URL can be built without the base URL, by automatically resolving to the current hostname (which serves as the proxy URL). Removing PROXY_HOST will simplify the configuration without impacting functionality.

Testing Details

  • Unit Test Added
  • Manual Test/Other (Please elaborate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

@illiakovalenko illiakovalenko requested a review from a team February 7, 2025 11:27
Copy link
Contributor

@yavorsk yavorsk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!
Just maybe remove the PROXY_HOST mention in the readme of angular-xmcloud.

@illiakovalenko illiakovalenko merged commit f1572af into dev Feb 7, 2025
1 check was pending
@illiakovalenko illiakovalenko deleted the feature/JSS-5054 branch February 7, 2025 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants