discovery-vsts/vsts-discovery-frontend

An education extension for MS VSTS.

An Extension for VSTS

Download from VSTS Marketplace

Build and Publish Extension into VSTS

Please follow this article.

Structure of this plugin

Modules and components

Each item in top navigation menu is corresponding to a module. All modules are under #module-area. (in following structure diagram, #ids are ids for html tags in index.html. those *.html are dynamically loaded page using JQuery.load())

#module-area
|-- #100-points-module
|    |-- #100-points-components
|        |-- #100pt-status --> 100-points-status.html
|        |-- #100pt-assign --> 100-points-assign.html
|-- #codetracker-module --> codetracker-status.html
|-- #setting-module --> setting.html

When nav bar is clicked, corresponding module section will be shown. By default the plug in will load 100-points-module on page load.

vsts-discovery-frontend's Issues

Current assign table refresh after submit

perhaps do a GET and refresh the table after submit points

bindTopNavClickEvents() not used?

Need all member to see current points assigned

Display some loading text in status

Add RequireJS

optimisation loading orders

Use VSS SDK to get git project id and member's email data

git project id/name

Remove operation drop down list

Configure and add datepicker

#100pointsAssignBranch Assign point to members

Edit members and points given in table
Submit to API
Check isFinal and display feedback

GPA text colour

Empty chart when no data

optional: Add regional settings

location based language settings or change language option for non-english speakers

Connect with backend API

Need selector to pick which repo to display

Probably need an endpoint for this: Get all repos by instance name

Convert Epoch to human readable datetime

Handle validated data correctly

When data has been validated there should be no option to assign points, just the distributed points for the week

Validate points correctly

Currently validate points does not validate points properly, JSON is correct however server does not handle request, need to look into this

Configure Pie chart to read and display weekly distribution points.

read API data
configure the chart
random color
selecteable date

Map emails in Pie chart with names

Display names instead of emails

Not load today in status

unknow names in piechart when first loaded

Send instance ID for each endpoint calls to 100-point backend

The id is global variable now. Just call "currentInstanceID"

Prevent repeat loading modules whenever menu item is clicked

History line chart scale

Convert current day of week to a date range

Currently the front end creates a date, however this must be changed to reflect the backend once it has been updated.

Decouple getMemebers() and UI functions

GPA N/A for value 0 or less than 0

Test new 100 point endpoints

Change datetimepicker to another one

Use this:
http://www.malot.fr/bootstrap-datetimepicker/

Implement accessibility options

Ensure front end contains metadata for use with screen readers and/or other accessibility equipment

Set initial module to 100 point status

Configure a Line chart to display one member's points change over time

Change datepicker to allows only for selecting weeks

Not Found text beside datepicker

Handle no JSON in point distribution

When there is no point distribution the front end should POST one to create one

Front end testing framework

Apply javascript testing to VSTS plugin

Create slack JSON message to send to back end

When creating a POST or PUT request the same JSON with an instance ID of the VSTS project should be sent to the slack service to be updated

Access-Control-Allow-Origin issue

Don't create a new Pie chart when every time the selected date is changed

Not use page load in assign component, change table generation bit into other event

Codetracker hardcoded parameters

Hide datepicker after click