The content of the app can spill over the borders, making it hard to select the buttons at the bottom.

The content should scale (preferred) or the app allow for scrolling.

If there are too many contributors the legend takes over the entire image.

Find a good workflow for developing on this project and ideally document the workflow.

Decided in the team meeting in week 8 that this should be as text rather than an image.

Github has a program for people who use their API. We will get updates/notifications of API changes. Also a neato badge.

We need a URL for our service, so wait until our app has an endpoint.
https://github.com/developer/register

Error handling for invalid user/repo/etc input e.g. a repo that doesn't exist

Perhaps just some screenshots inserted into the help section.

I am creating accordion using library ui-botstrap-tpls-0.14.3.min.js.

But as far as I have experimented with ui-bootstrap accordion, it only lets the developer specify the content inside .panel-title, everything goes inside

{{heading}}

In our UI we only have

tag, so to maintain the hierarchy, we need

tag instead of

tag.

Please suggest how we can customize it in code to get

tag without customizing the .library file.

Thanks

Take the existing static views and make them into a functional UI.
@dcrawfordtcd (mentioned since GitHub only allows single assignees)

Githubs API will sometimes return an empty response if they have not recently calculated the stats for a repository or user. Add a retry if an empty response is returned.

Suggestions to be put in the group chat.

Write some javascript to create an image of a pie chart.
The pie chart should ideally be created using the Office library.

The reason for working on a pie chart over other graphs is that 1. a pie chart is a relatively simple graph and 2. we can use the pie chart to show some simple data for Tuesday such as the amount of commits per user to a repo.

so that the week reads from the top down rather than the bottom up.

sometimes it's just the first few letters in the word that comes up as an x-axis label, and sometimes it's not really a problem cause you know what it would mean anyway.
but the way that the crop cuts off the labels on the x-axis label for the punchcard makes it look completely wrong.
If the time is a 2 digit number it cuts off the first digit, so that 10am looks like 0am, 12pm looks like 2pm and also you then can't tell the difference between 12pm and 2pm for example.

This would be fixed with cropping the image when it's created. I had a look myself but i've no idea how do do it.
This is also an issue with every other picture that's generated, but punchcard is the worst affected.

Write some JavaScript which, using the GitHub API, retrieves information necessary for each of the graphs that we would like to generate. Each of these graphs is documented here.

There is already an example using the gh3 library for fetching user data from GitHub.

One API call to work on is commits per user to a repo which we could then display using a pie chart for the Tuesday demo. Pie chart is being worked on in this issue #4 .

A simple UI which should follow the mockup in the requirements doc.

Note that the linked mockup is missing back buttons.

Priority should be given to an initial page for selecting graphs, a page for a single graph with appropriate input fields, followed by the final page which you can see in the requirements doc.

Once that is all done you could:

• add a page for every graph that's in the requirements doc
• ensure that pages are only shown for graphs that were selected on the initial page
• error checking such as ensuring that at least 1 graph is selected on the initial page

If styling the UI this should be done using the microsoft fabric library. See index.html and fabric.

Write a test which ensures that one of the calls to the GitHub API returns the correct response.
This could be done using a JavaScript unittest plugin such as Mocha and integrating it with Gulp such that we could run gulp test to see if our tests are passing or not.

Lots of error handling is duplicated code. It shouldn't be.

Fix the x-axis to show suitable date values

Insert the image logged in contributions-page.html to an Office document.

Certain input fields exist in multiple input pages. When one of these input values changes on one page, the value should be updated on any other pages.