Skip to content

Upgrade sparkles components to glimmer #288

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 22 commits into from
Apr 21, 2020
Merged

Conversation

mansona
Copy link
Member

@mansona mansona commented Feb 14, 2020

This includes an update with ember-cli-update so that we can start making use of Octane things

@mansona mansona requested a review from a team February 14, 2020 11:53
@mansona mansona force-pushed the upgrade branch 4 times, most recently from 8f5d8fe to c7f3a7e Compare February 14, 2020 16:18
@locks
Copy link
Contributor

locks commented Feb 28, 2020

Conflicts ahead!

@mansona
Copy link
Member Author

mansona commented Feb 28, 2020

@locks the conflicts aren't the thing that is currently blocking this. I am chatting to @rwjblue and @pzuraq about the co-location polyfill which I personally think is currently a blocker for this PR 🤔

@mansona mansona force-pushed the upgrade branch 2 times, most recently from a1ba310 to dd03a7e Compare March 31, 2020 09:41
@mansona
Copy link
Member Author

mansona commented Mar 31, 2020

There seems to be some sort of bug that is preventing me to move any of the addon/components/es-footer-*.hbs components into a non-colocated position 🤔 I don't know what's going on here

@mansona
Copy link
Member Author

mansona commented Apr 1, 2020

This is currently blocked by #301 and is blocking #300 👍

@mansona mansona added the blocked 🛑 this issue is blocked by something else. label Apr 1, 2020
@MelSumner
Copy link
Member

Looks like this has some conflicts @mansona

@mansona
Copy link
Member Author

mansona commented Apr 16, 2020

@MelSumner I mention in my last comment that this is blocked by #301 so I'm going to wait until that is merged before I fix any conflicts 👍 I'll add a note to the main description too

@mansona mansona removed the blocked 🛑 this issue is blocked by something else. label Apr 20, 2020
@mansona mansona dismissed RobbieTheWagner’s stale review April 20, 2020 20:49

this PR has changed a lot since this review

@mansona mansona requested review from a team April 20, 2020 21:27
@@ -1,9 +1,10 @@
import Component from '@ember/component';
import layout from './template';
import layout from 'ember-styleguide/templates/components/es-header-navbar-link';
Copy link
Contributor

Choose a reason for hiding this comment

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

could we keep the relative import?

Copy link
Member Author

Choose a reason for hiding this comment

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

I would prefer not to because none of the other components have it, we really should upgrade this to Glimmer after this is merged but it's not a blocker for release

I also moved this because of the bug we discussed with ember-angle-bracket-invocation-polyfill, we can't use nested angle bracket components any more so I needed to move the component 👍

this.setupLinkBlurs();
if (this.isDropdownOpen) {
// if it's open, let's make sure it can do some things
schedule('afterRender', this, function() {
Copy link
Contributor

Choose a reason for hiding this comment

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

this needs to go ASAP after the merge

Copy link
Member Author

Choose a reason for hiding this comment

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

I am planning on creating an issue after this is merged to convert this component into a glimmer component and I will make sure there is a todo item to remove the runloop stuff too 👍

}
</style>

<div class="layout mt-3">
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't really understand this change 🤔 Is the idea to move the piece of data somewhere?

Copy link
Member Author

Choose a reason for hiding this comment

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

Just copying the explanation I had in a DM here:

Essentially the <ColourPallet /> component is now coming from upstream (Field Guide) and because of that we had to add some arguments to each of these entries. Instead of exploding the size of these components with a lot of duplicated arguments I thought it would be "simpler" to restructure the page, although I'm happy to revert this if it's a blocker and too complicated 👍

@mansona mansona merged commit bbb659f into website-redesign-rfc Apr 21, 2020
@amyrlam amyrlam deleted the upgrade branch June 25, 2020 06:02
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