Implement detail page skeleton - #80
Conversation
| .li-dropdown { | ||
| color: #999; | ||
| color: #555; | ||
| position: relative; |
There was a problem hiding this comment.
What was the reason for this change?
There was a problem hiding this comment.
@na3d pointed out that the width of the dropdown's contents don't match up with the width of the dropdown. This fixes that.
There was a problem hiding this comment.
(with the help of other changes)
There was a problem hiding this comment.
Ah. I wouldn't worry about this too much. It's too complex and arbitrary. I do not expect for much of the dropdown code to remain for long.
There was a problem hiding this comment.
Cool. I was thinking that an overhaul of the dropdowns was probably necessary. Want to backlog it?
Update a few styles
|
This is ready for review+merge once build passes. |
|
👍 |
| this.renderHeader = this.renderHeader.bind(this); | ||
| this.renderEditUI = this.renderEditUI.bind(this); | ||
| this.renderLabel = this.renderLabel.bind(this); | ||
| this.handleLabelKeyUp = this.handleLabelKeyUp.bind(this); |
There was a problem hiding this comment.
It's a little late, but I am not a big fan of this.
There was a problem hiding this comment.
Reassigning the same variable with this bound.
There was a problem hiding this comment.
This is a common React pattern. We don't really have a choice. They need to be bound to this.
There was a problem hiding this comment.
- they don't need to be bound to a variable 2) they don't need to be bound to the same variable.
There was a problem hiding this comment.
They will only cause errors in certain contexts - generally if someone just doesn't know what they're doing.
There was a problem hiding this comment.
That's not true. If we have correct test coverage (which we should verify on each PR) they will always verify every code path, including the ones that would use this and then fail.
There was a problem hiding this comment.
There's still nothing to stop someone from not doing this.callback = this.callback.bind(this) and calling <Thing onClick={this.callback.bind(this)} /> instead and so forth.
There was a problem hiding this comment.
We shouldn't defy established convention because it gives you the willies. Your solution also introduces more boilerplate and transfers responsibility for binding to the caller, where I expect mistakes are more likely to happen. 👎
There was a problem hiding this comment.
I'm saying your suggestions are less valid.
|
ready for merge? |
|
Yes. |
|
Thanks. |
upcoming: [DI-21119] - token call fix for differently ordered same resource ids..
…1109] Improve Vitest setup w/ shards"
Merge in FEE/cloud-manager from chore/cicd-tests to develop
Squashed commit of the following:
commit 8f53c371bb83fa794a3dd948f954b0ecd233f4ea
Author: Conal Ryan <corya@akamai.coms>
Date: Fri Apr 17 12:45:56 2026 -0400
Revert "Pull request linode#73: chore: [UIE-11109] Improve Vitest setup w/ shards"
This reverts commit 4cb03e5.
…1109] Improve Vitest setup w/ shards"
Merge in FEE/cloud-manager from chore/cicd-tests to develop
Squashed commit of the following:
commit 8f53c371bb83fa794a3dd948f954b0ecd233f4ea
Author: Conal Ryan <corya@akamai.coms>
Date: Fri Apr 17 12:45:56 2026 -0400
Revert "Pull request linode#73: chore: [UIE-11109] Improve Vitest setup w/ shards"
This reverts commit 6683d46.
…e Vitest setup w/ shards"
Merge in FEE/cloud-manager from chore/cicd-tests to develop
Squashed commit of the following:
commit 8f53c371bb83fa794a3dd948f954b0ecd233f4ea
Author: Conal Ryan <corya@akamai.coms>
Date: Fri Apr 17 12:45:56 2026 -0400
Revert "Pull request #73: chore: [UIE-11109] Improve Vitest setup w/ shards"
This reverts commit ae3f7f6.
Closes #30. I still have to write all of the tests for this.