-
Notifications
You must be signed in to change notification settings - Fork 117
Colors theme fixes #2186
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
Merged
Merged
Colors theme fixes #2186
Changes from 2 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
dc71cb4
fix powergraph
cshagen 6decd61
fix time display format
cshagen a0affbb
remove vite server.allowedhosts
cshagen d479096
cleanup
cshagen 6d06a25
cleanup
cshagen 3958af6
prettify vite.config.ts
cshagen d883e47
prettify vite.config.ts
cshagen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
6 changes: 0 additions & 6 deletions
6
packages/modules/web_themes/colors/web/assets/index-CIr-OUyK.js
This file was deleted.
Oops, something went wrong.
6 changes: 6 additions & 0 deletions
6
packages/modules/web_themes/colors/web/assets/index-CaUGgs4L.js
Large diffs are not rendered by default.
Oops, something went wrong.
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Abgesehen davon, dass die Einrückung nicht passt: warum ist diese Einstellung erforderlich? Ich sehe keine Grund.
Laut Doku wird dringend davon abgeraten. https://vite.dev/config/server-options#server-allowedhosts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ohne das bekomme ich mit der aktuellen Vita-Version diese Fehlermeldung im Browser, wenn das Theme lokal starte:
Es hilft aber nicht, wenn ich meinen internen Hostnamen auf Github poste, ausserdem kann der ja auch mal ändern. Die Config sollte ja auch nur dann greifen, wenn das Colors-Theme lokal mit "npm run dev" gestartet wird. Es sollte daher für den normalen Betrieb keinen Sicherheitsabstand-Impact geben.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Der Zugriff per IP reicht Dir nicht?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Danke für den Tipp. IP-Adresse funktioniert. Ich habe die server.allowedHosts-Config wieder rausgenommen.