This PR doesn't upgrade components to be Glimmer components yet. It's already big enough as it is.
@galfert I'm not sure if you saw my chat message, but when you look at the tests you can find one helper failing (due to some kind of observer issues), and that one failure also seems to break the entire run loop of the Ember app when using it normally, thus freezing the app in place when it hits (which is when you look at contribution details). Hence the WIP.
I also removed all code relating to proposals on the way, as we're not using them at all at the moment. Thus, dragging the code along through big upgrades like this one didn't make sense to me. We can always retrieve it from Git whenever we need it again.
This PR doesn't upgrade components to be Glimmer components yet. It's already big enough as it is.
@galfert I'm not sure if you saw my chat message, but when you look at the tests you can find one helper failing (due to some kind of observer issues), and that one failure also seems to break the entire run loop of the Ember app when using it normally, thus freezing the app in place when it hits (which is when you look at contribution details). Hence the WIP.
I also removed all code relating to proposals on the way, as we're not using them at all at the moment. Thus, dragging the code along through big upgrades like this one didn't make sense to me. We can always retrieve it from Git whenever we need it again.
fsmanuel
(Migrated from github.com)
reviewed 2020-05-11 08:39:29 +00:00
Haha, now I wonder how it ever NOT caused an exception :) There was a typo in the property name in the function that removes the observer. I guess older Ember versions kept track of existing observers in a different way that didn't fail when trying to remove a non-existent observer.
Haha, now I wonder how it ever *NOT* caused an exception :) There was a typo in the property name in the function that removes the observer. I guess older Ember versions kept track of existing observers in a different way that didn't fail when trying to remove a non-existent observer.
Code looks good to me. Just left some minor comments.
But the kredits amount in the "Confirmed Contrubutions" list looks misaligned now:
Code looks good to me. Just left some minor comments.
But the kredits amount in the "Confirmed Contrubutions" list looks misaligned now:
<img width="616" alt="kredits" src="https://user-images.githubusercontent.com/843/81553971-4625bb00-9386-11ea-9527-dce066bf6646.png">
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR doesn't upgrade components to be Glimmer components yet. It's already big enough as it is.
@galfert I'm not sure if you saw my chat message, but when you look at the tests you can find one helper failing (due to some kind of observer issues), and that one failure also seems to break the entire run loop of the Ember app when using it normally, thus freezing the app in place when it hits (which is when you look at contribution details). Hence the WIP.
I also removed all code relating to proposals on the way, as we're not using them at all at the moment. Thus, dragging the code along through big upgrades like this one didn't make sense to me. We can always retrieve it from Git whenever we need it again.
Haha, now I wonder how it ever NOT caused an exception :) There was a typo in the property name in the function that removes the observer. I guess older Ember versions kept track of existing observers in a different way that didn't fail when trying to remove a non-existent observer.
@galfert Thanks!
So this is ready to review/merge then.
I'm already reviewing it.
Code looks good to me. Just left some minor comments.
But the kredits amount in the "Confirmed Contrubutions" list looks misaligned now:
Did you remove the use of the
contribution-statushelper because of the bug or is it just not needed here anymore?@@ -1,42 +1,44 @@{{#if showIntroText}}<div id="intro" class={{if showDetailsPane "with-details"}}>{{#if this.showIntroText}}I think the
idattribute is not supposed to be prefixed with the@.This file shouldn't be committed. Probably needs a
.gitignorerule.@@ -1,55 +1,56 @@<form {{action "submit" on="submit"}}><form onsubmit={{action "submit"}}>No
@forid,placeholderandclass, but one should be added tovalue.Yes, because of the bug. But this was an accidental commit. I just needed it locally to work on the rest.
Thanks!
(I cannot reproduce the misalignment of the amounts.)
Looks ok here now, too. I think it was the missing contribution-status class.