Fix missing documentation redirects in Docker frontend build - #132
Merged
Merged
Conversation
This file contains hidden or 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
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.
The frontend imports
wavedoc/redirects.json, but thefrontend-builderDocker stage only copied the editor and frontend trees. A clean Docker build therefore failed with TS2307 even though building from a complete checkout passed.Copy the shared JSON into the frontend stage before compilation. Add a CI build of that exact Docker stage before other steps generate local dependencies or artifacts, so missing build inputs cannot pass unnoticed again.
Verification
frontend-builderstage successfully.git diff --check.