Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 3.8k
v0.7.23: comparison table, security hardening, subflow & streaming improvements #5421
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
Uh oh!
There was an error while loading. Please reload this page.
Changes from all commits
0249516818fa0082eff54acf4afb04432b6b98c7c41a371e5a1fbb5741fb8630d6994d4b13398f456ed93edaae3ee1824c82eb6dc85f80faFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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.
globals.css, which the team style rule reserves for cases where a local component file genuinely cannot carry the change.::selectionis a global pseudo-element that cannot be scoped to a single component, so the change is functionally justified — but the new--selection-mutedvariable is only consumed by::selection, so it could be inlined as a literal there instead of adding two new global custom properties.Rule Used: Avoid editing the globals.css file unless absolute... (source)
Learned From
simstudioai/sim#367
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!