Skip to content
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

adding sub-tabs for listings in progress #174

Merged
merged 1 commit into from
May 21, 2018

Conversation

nickreynolds
Copy link
Member

also:

  • fixing bug in core related to can challenge be resolved

@nickreynolds nickreynolds requested review from am9u and walfly May 21, 2018 19:23
…to can challenge be resolved

removing logs

running prettier
@nickreynolds nickreynolds force-pushed the nickreynolds/listing-sub-tabs branch from f25d3b5 to e053451 Compare May 21, 2018 19:29
@coveralls
Copy link

coveralls commented May 21, 2018

Pull Request Test Coverage Report for Build 3290

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 87.539%

Totals Coverage Status
Change from base Build 3276: 0.0%
Covered Lines: 581
Relevant Lines: 625

💛 - Coveralls

@@ -63,5 +63,5 @@ export function canResolveChallenge(challengeData: ChallengeData): boolean {
* @param challengeData this ChallengeData to check
*/
export function doesChallengeHaveAppeal(challengeData: ChallengeData): boolean {
return !challengeData.appeal || is0x0Address(challengeData!.appeal!.requester.toString());
return challengeData.appeal! && !is0x0Address(challengeData!.appeal!.requester.toString());
Copy link
Contributor

Choose a reason for hiding this comment

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

Durrrr. Thanks for fixing this.


class ListingsInProgress extends React.Component<ListingProps> {
public render(): JSX.Element {
const applications = this.props.applications;
Copy link
Contributor

Choose a reason for hiding this comment

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

should these be represented in the reducers? Like instead of merging them here, get rid of the smaller categories and replace them with meaningful sets?

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'd rather keep the small categories at least for now. Don't think we're even sure what exactly the bigger categories would be, this makes it a bit easier to change things around?

@nickreynolds nickreynolds merged commit cac167e into master May 21, 2018
@ritave ritave deleted the nickreynolds/listing-sub-tabs branch June 20, 2018 11:01
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.

None yet

4 participants