-
Notifications
You must be signed in to change notification settings - Fork 27
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
Default route configuration is ignored when visiting the root path bug fix #1871
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cquirosj
force-pushed
the
read_defaultRoute
branch
from
June 7, 2024 02:23
1a3add8
to
3b12e09
Compare
cquirosj
approved these changes
Jun 7, 2024
TravisNickels
approved these changes
Jun 7, 2024
src/Frontend/test/specs/installation-config/app-constants.spec.ts
Outdated
Show resolved
Hide resolved
src/Frontend/test/specs/installation-config/app-constants.spec.ts
Outdated
Show resolved
Hide resolved
Co-authored-by: Travis Nickels <travis.nickels@particular.net>
Co-authored-by: Travis Nickels <travis.nickels@particular.net>
cquirosj
changed the title
set default route according to setting in app.constants
Set default route according to setting in app.constants.js
Jun 24, 2024
cquirosj
changed the title
Set default route according to setting in app.constants.js
Bug fix: ServicePulse should automatically navigate to the specified path in app.settings.js default_route property upon loading
Jun 24, 2024
cquirosj
changed the title
Bug fix: ServicePulse should automatically navigate to the specified path in app.settings.js default_route property upon loading
ServicePulse should automatically navigate to the specified path in app.settings.js default_route property upon loading
Jun 24, 2024
cquirosj
changed the title
ServicePulse should automatically navigate to the specified path in app.settings.js default_route property upon loading
ServicePulse should automatically navigate to the specified default route upon loading
Jun 24, 2024
cquirosj
changed the title
ServicePulse should automatically navigate to the specified default route upon loading
ServicePulse doesn't navigate to the specified default route upon loading bug fix
Jun 24, 2024
cquirosj
changed the title
ServicePulse doesn't navigate to the specified default route upon loading bug fix
Default route configuration is ignored when visiting the root path bug fix
Jun 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When ServicsePulse is visited on the root path (/) it should automatically navigate to the path specified in /js/app.constants.js, default_route property. See "Install ServicePulse in IIS" for more information on how to extract ServicePulse files.