charlottedevs / client Goto Github PK

Currently, there's only an onHover effect. Would be nice if we put currentRepo in redux state in the repos-reducer. Then we can keep the current nav item highlighted so users know which repo they're viewing issues.

Add a favicon instead of using the default React logo generated from create_react_app.

Repos are being served from the API in this format:

{name: "api", path: "charlottejuniordevs/api", open_issues_count: 4}

We can use open_issues_count in the response to put a badge on every repo nav item with the appropriate count.

Everything should be first letter capitalized, IMO.

Let's add a little bit of copy to tell users what the leaderboard is.

My JS console shows this error:

XMLHttpRequest cannot load https://cltjrdevsapi-qa.herokuapp.com/credibility. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://challenges-qa.charlottejuniordevs.com' is therefore not allowed access. The response had HTTP status code 503.

This is indicative of a cross-site scripting problem (perhaps as simple as http vs https, but is likely a config issue that @binarymason may need to dig into)

Add comments count to challenges card so users can tell if a particular issue has activity or not.

Maybe something happy and green? 💚

Make the images within challenge cards resize to fit the card entirely so users don't have to scroll to see the rest of an image

When a user submits a change to their account settings, and a validation error occurs from the API response, the error message(s) should be displayed next to the field to let the user what went wrong.

Example error response:

{  
   "errors":{  
      "github_handle":[  
         "has already been taken"
      ],
      "email":[  
         "can't be blank"
      ],
      "first_name":[  
         "can't be blank"
      ],
      "last_name":[  
         "can't be blank"
      ]
   }
}

Have the API send javascript time and make the client convert the time to whatever is local to a user's machine.

Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead

Instead of:

import React, { PropTypes } from 'react';

Change to:

import PropTypes from 'prop-types';

Note:
You will need to add prop-types as a dependency by running:

npm install --save prop-types

Pro Tip:
Use a command-line tool like ag to easily search across files for specific content, ie:

ag "import React, { PropTypes } from 'react'"

Pretty self explanatory - when I login, it looks like Google has accepted the OAuth authentication, but the page doesn't change to reflect the successful login

Things like a twitter handle should resolve to https://twitter.com/<handle> not to charlottejuniordevs.

Even though I follow the example URL, when I save and view my profile the link is not saved

We should be taking advantage of React and using local styling instead of the global styles we are currently using.

It's possibly related to #19 , but since I haven't verified that yet, this is a separate issue.

I changed the description for the following issue on the API repo and the change wasn't reflected in the description card on the charlottejuniordevs challenges page:
https://github.com/charlottejuniordevs/api/issues/5

On the challenges homepage, add copy explaining the intent behind code cred and how to get it.

It's confusing people and suggesting that they include a @ which in fact, we don't want that.

Navbar should break down better.

A responsive side nav would be great.

The onHover effect works, but the outer edges of the button are not hyperlinked.

The API appears to be down right now according to my console:

OPTIONS https://cltjrdevsapi-qa.herokuapp.com/credibility 503 (Service Unavailable)

This issue is addressing the near-blank screen that I have due to this service being down, perhaps a better fallback mechanism is in order?

The expected behavior is users with same score should be in the same place on leaderboard.

Go to /asdfasdf and you'll know what I mean.

It should point to http://faq.charlottejuniordevs.com

GitHub sends a labels array for issues that looks like this:

(json)
...
    "labels": [
      {
        "id": 208045946,
        "url": "https://api.github.com/repos/octocat/Hello-World/labels/bug",
        "name": "bug",
        "color": "f29513",
        "default": true
      }
    ],
...
(more json)

When a user views a challenge that is a GitHub issue, it should include the name of all labels, if they exist. Additionally, the labels should have a colored background using the hex code in the color attribute.