Skip to content

Implement detail page skeleton - #80

Merged
eatonphil merged 16 commits into
masterfrom
feature/detail-page-skeleton
Jun 8, 2016
Merged

Implement detail page skeleton#80
eatonphil merged 16 commits into
masterfrom
feature/detail-page-skeleton

Conversation

@ddevault

@ddevault ddevault commented Jun 7, 2016

Copy link
Copy Markdown
Contributor

Closes #30. I still have to write all of the tests for this.

.li-dropdown {
color: #999;
color: #555;
position: relative;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What was the reason for this change?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@na3d pointed out that the width of the dropdown's contents don't match up with the width of the dropdown. This fixes that.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(with the help of other changes)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool. I was thinking that an overhaul of the dropdowns was probably necessary. Want to backlog it?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure

@ddevault

ddevault commented Jun 8, 2016

Copy link
Copy Markdown
Contributor Author

This is ready for review+merge once build passes.

@ddevault ddevault changed the title [DO NOT MERGE] Implement detail page skeleton Implement detail page skeleton Jun 8, 2016
@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage increased (+6.2%) to 75.887% when pulling 3e52a11 on feature/detail-page-skeleton into 208b744 on master.

@na3d

na3d commented Jun 8, 2016

Copy link
Copy Markdown
Contributor

👍

this.renderHeader = this.renderHeader.bind(this);
this.renderEditUI = this.renderEditUI.bind(this);
this.renderLabel = this.renderLabel.bind(this);
this.handleLabelKeyUp = this.handleLabelKeyUp.bind(this);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a little late, but I am not a big fan of this.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A fan of what?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reassigning the same variable with this bound.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a common React pattern. We don't really have a choice. They need to be bound to this.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. they don't need to be bound to a variable 2) they don't need to be bound to the same variable.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They will only cause errors in certain contexts - generally if someone just doesn't know what they're doing.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@eatonphil eatonphil Jun 8, 2016

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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. 👎

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm saying your suggestions are less valid.

@eatonphil

Copy link
Copy Markdown
Contributor

ready for merge?

@ddevault

ddevault commented Jun 8, 2016

Copy link
Copy Markdown
Contributor Author

Yes.

@eatonphil
eatonphil merged commit 02022c0 into master Jun 8, 2016
@ddevault
ddevault deleted the feature/detail-page-skeleton branch June 8, 2016 19:14
@ddevault

ddevault commented Jun 8, 2016

Copy link
Copy Markdown
Contributor Author

Thanks.

nikhagra-akamai pushed a commit to nikhagra-akamai/manager that referenced this pull request Nov 22, 2024
upcoming: [DI-21119] - token call fix for differently ordered same resource ids..
abailly-akamai pushed a commit to abailly-akamai/manager that referenced this pull request Apr 22, 2026
…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.
grevanak-akamai pushed a commit to grevanak-akamai/manager that referenced this pull request Apr 23, 2026
…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.
grevanak-akamai pushed a commit that referenced this pull request Apr 23, 2026
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants