Fixed too early initialization of view compilation service #1809
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
exyi
approved these changes
Apr 27, 2024
tomasherceg
force-pushed
the
fix/early-resolve-view-compilation-service
branch
from
745a8a0
to
c46dcd3
Compare
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.
Adding HealthChecks this way caused
IDotvvmViewCompilationServiceandDotvvmConfigurationto resolve too early on the startup.Because of that,
configuration.Debugwas not set yet totrueand even in the development mode, DotVVM was not reloading modified markup files until the application got restarted.This PR goes to
4.2, but we should cherry-pick it tomainalso.