-
Notifications
You must be signed in to change notification settings - Fork 751
[SourcesTree] Style debuggee URL domain #4463
[SourcesTree] Style debuggee URL domain #4463
Conversation
|
That's really cool, looks good! |
src/components/shared/Svg.css
Outdated
| } | ||
|
|
||
| .domain.debuggee { | ||
| fill: lightgreen; |
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.
Note: Maybe there's a green defined in the themes we can use here @jasonLaster?
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.
var(--theme-toolbar-highlighted-color) ?
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.
@nt1m I tried your suggestion and here is a screenshot of what I got:
To tell you the truth, I like green color more.
wldcordeiro
left a comment
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.
Nice job @svitlana-galianova I like the result of this. Just a note on the color choice but I think it looks great.
|
@wldcordeiro thanks! It won't be a problem to change a color to whatever you think is the most suitable. |
| return <Svg name="domain" />; | ||
| return <Svg name="domain" | ||
| className={classnames({ | ||
| debuggee: (this.props.debuggeeUrl != null && item.name != null && this.props.debuggeeUrl.indexOf(item.name) !== -1) ? true : false |
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.
This can be simplified to:
debuggee: this.props.debuggeeUrl && item.name && this.props.debuggeeUrl.includes(item.name),You don't need the ternary that does true : false since your condition is already a boolean.
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.
You do need the != null checks to avoid Flow complaining about sketchy existence checks.
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.
@nt1m Thanks for your comment, I thought it would be smarter to use indexOf since it's supported in all the browsers and includes is only supported in the following browsers (according to w3school):
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.
Don't worry about browser support, we use includes in other areas of the code base, you can feel safe using it :). For most cases, we have Babel, which transpiles es6 where necessary (so you will see things like spread operators which are not available everywhere being used already!) so feel free to explore modern JS as much as you like! our primary targets are modern chrome and firefox.
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.
@codehag Thanks for your clarification!
src/components/shared/Svg.css
Outdated
| } | ||
|
|
||
| .domain.debuggee { | ||
| fill: lightgreen; |
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.
var(--theme-toolbar-highlighted-color) ?
…nd uncomputed memberexpressions
…ols#4427) * Update PaneToggle.css * Update Tabs.css * fix for dynamic width * error check for no element * moving ui related utilities to utils/ui file * adding export to each function
…t-sidebar-on-pause-at-breakpoint fix firefox-devtools#4471 - expand the right sidebar on pausing at breakpoint
Fix for firefox-devtools#4469 Right-click in editor window shows 2 context menus
Move workflow to pr docs
* Update Pause Semantics
* Add gitattributes * fix: Multi-platform and configuration issues This configures all systems to checkout and use LF line endings. The jest test system also runs without colors by default now. This allows the tests to pass in any environment regardless of color scheme. * tweaks
…nel_weirdness Close ConditionalPanel on blur
There were some race issues with the quick open mochitest assertions that this cleared up.
Added some tips to the mochitest debugging docs based on experience debugging race issue. Also Prettier fixed some things.
…pen-mochi Fix quick open mochi
* add terminology * Update terminology.md
|
Uh oh, this looks like it needs a rebase. It's gotten a lot of additional commits on it that aren't part of the PR. |
|
I feel like this pr got stuck in the proverbial git mud, so i cherrypicked the good stuff and put it in a new PR #4536 @svitlana-galianova you're still the author of the new PR's commit. Thanks for the hard work while we figured out what to do here. |
|
Passing by comment: it looks like you have worked directly on the master branch of your fork. Sadly, when using a fork, things will become unmanageable really fast, especially on a repository with a lot of changes like Debugger. The safest workflow is to keep your master in sync with the original repository's master, and create a branch to work on pull requests. At that point, if needed, you'd only need to rebase your branch against master. Once you have completed all the pending work, my personal suggestion would be to "reset" your master and sync it with this repository's master, so you have a clean starting point for future work. |
Associated Issue: #4259
Summary of Changes
Test Plan
Tell us a little a bit about how you tested your patch.
Example test plan:
Screenshots/Videos (OPTIONAL)