felixrdl / seeance Goto Github PK

Expected Behavior: Typing the name of a private repository should show the name in autocomplete, if the user is authorized for accessing it.

Experienced Behavior: The repository will not show up in autocomplete

Severity: This is critical, as student repos are often private

Currently, the analysis visualisations flicker on scroll. This may be due to repeatedly setting the inner html of the iframes

All features referring to the analysis framework.

• Registering requires also acknowledging the terms of usage.
• Registering is only possible, if the user is not already registered in the system.

Backend

• Create MongoDB Container
• Use mongoose ODM
• Add User Repository + Provider
• Define User Entitiy
• Define User Model
• Add Use Case
• Implement Use Case and connect it to routes

Frontend

• Create register landing page
• Implement User Service
• Implement register and create user
• Implement Registered User Route

#1 #2

Requirements:

• Know which analyses previously have been added
• Request confirmation to prevent accidential delete

Technical:

• Also delete all caches?

#5

#5

• Only registered Users can be authorized
• Needs an Autocomplete on registered users x Github Account
• A user cannot be added twice to a course (duh)

Backend

• Use Case GetAuthorizeesForCourse

• Use Case GetUserAutocomplete + Repository function

• Use Case PostuserToCourse

-- Check if user is already added

• Link Use Cases

• Owner must not be able to be added to authorizees

• Add authorized courses to /course endpoint

• Protect all course related contents

Frontend

• Implement Service Methods

• Implement Authorizee List

• Implement Authorizee Autocomplete

#3 #2

• this user story only refers to meta-data of the course, such as its name and description
  #3

• this requires the requestor to be at least authorizee or owner of the course
• this has to be confirmed by a dialog window
• this has to return 404, if the resource is not existing
• deleting the course also requires deleting all associated projects

backend

• add use case and repo functions
• check for existence of course
• implement user authorization
• implement repo function
• also delete projects for course!
• link up stuff

frontend

• add service method
• add GUI buttons for deletion
• add confirm dialogue
• add error handling
• link up stuff

#3

Everything related to allowing for the right users to access the right stuff.

Backend

• Add logic layer for "Add Analysis To Project" Use Case
• Implement and connect "Add Analysis To Project" Use Case

Frontend

• Add data service for plugin retrieval
• Add data service method for post request
• Add tab in config
• Add analysis autocomplete component
• Link everything together

Currently: The system allows accessing unauthorized items, as long as they are held in cache.
By requirement, the system must decline access on these resources.

Requirements

• check authorization of user for repository on github
  -- if repository is public, allow access
  -- if repository is private and user owns the repository, allow access
  -- if repository is private and user is contained in collaborators list, allow access
  -- else access is declined

• display unauthorized projects separately (e.g. as grayed out symbol or "" label

Backend

• At first, a good caching strategy for content should be introduced.

#1 #2 #3

• this requires initializing
  -- a angular2 project
  -- a expressjs server
  -- a docker-compose project
  -- dockerfiles for both projects
  -- an nginx reverse proxy
  -- ssl
  #19

Requirements

• Authorization for github repository of logged-in user

Technical

• As it is very laborous, this may need a whole lotta caching on backend side (e.g. cached-request js, or manually saving temporary products)

Backend

• Create "GetAnalysisResult" Use Case
• Implement and Link "GetAnalysisResult" Use Case

Frontend

• Create Service Method
• Implement "Mosaique" for analyses

#5

Backend-Tasks

• Create configure preproc use case
• Link up use case

Frontend-Tasks

• Implement backend service
• Implement preproc config component

#3 #4 #2

Requirements

• Analyses self-describe their configuration

Technical

• Embedding System must not know about specific configuration of plugin

Backend-Side

• Implement GetAnalysisTemplateByNameTemplate UseCase
• Implement GetAnalysisById Use Case
• Implement Store Configuration Use Case
• Bootstrap everything

Frontend-Side

• Implement service functions
• Implement form renderer based on json-schema-form (https://www.npmjs.com/package/angular6-json-schema-form -> will this work with ng 9?)

#5

Backend Tasks:

• Implement DeletePreprocessors/Analyses + RemoveFromProjectPreprocessors/Analyses Use Cases
• Implement Repository operations
• Link everything up (DEL /analyses/:id - /preprocessors/:id)

Frontend Tasks:

• Implement Services
• Add delete buttons to lists

Backend

• Implement list courses use case
• Implement list own courses repository method
• Implement routing

Frontend

• Implement list courses service method
• Implement navbar course list
• Link and embed navbar behavior

#3 #2

Currently, the module only renders text input fields correctly, but no dropdowns, radio selects etc.

•  Implement request mapping in "webserver" layer and adapt controllers
•  Move Providers and Security to driver layer
•  Move "models" into providers
•  move "webserver" into "interfaces"

Requirements

• Account can only be deleted by authorized user her- or himself
• Deleting the account will also delete all courses created by the user.
• Deleting the account will remove the user from all projects, where he or she has been authorized.
• Deleting the account will remove all projects owned by user and their configurations

Backend

• Add DeleteUserById, DeleteProjectsForUser, DeleteProjectsForCourse Repository functions
• Add DeleteUseryByIdUserCase
• Link everything up

Frontend

• Add Profile Module
• Add Profile Root Component
• Add DeleteUserComponent
• Add Service Method
  #1

• this requires the user to be actually be authorized for the course
• the user cannot be the owner of the course
  #1 #3

For easier development, the backend should be tested through automatic testing utilities
#19

#1

Everything related to managing an individual github repository within a course.

Login is handled via Github OAuth:

NGINX

• Add Proxy Route to Login

Frontend

• Initialize Visual Framework
• Initialize Auth Service
• Add Link to Github Auth in Header
• Add Callback Route for Login
• Setup Callback Link in Github
• Store Token In Cookies within Auth Service

Backend

• Add Middleware for Token Validation

Frontend

• Add Guard Route For Token Validation

#1

• Courses are identified by a name
• Courses can be also refered to in a short description
• Duplicate course names are not allowed for the same user
• Beware of illegal characters, such as /

Backend

• Define Course Entity and Course Schema
• Define Course Provider
• Define Provider Functions 'Get Course' and 'Has Course By Name'
• Define Create Course Use Case
• Create Course Controller
• Create Course Routes
• Link and Test Components

Frontend

• Create Course Service
• Create Sidenav
• Create Course Editor

#3

Backend Components

• Implement ListPreprocessorTemplates, GetPreprocessorTemplateByName, CreatePreprocessor, AddPreprocessorToProject Use Cases
• Link everything up

Frontend Components

• Create Backend Service Counterparts
• Create Select PreprocessorDialog
• Create List of Preprocessors

Everything related to the internal account of a user.

Requirements

• know which analyses are possible
• select one analysis
• pre-configure analysis with good defaults

#5

• courses to be deleted have to be actualy registered in the project

Backend

• Add and implement repository method
• Add DeleteProjectByIdFromCourse Use Case
• Implement ProjectNotRegisteredForCourse
• Link and route use case

Frontend

• Add delete method in service
• Add delete buttons for items
• Link everything

#3 #4

• this requires an autocomplete for valid projects
• valid projects are projects, that the user can currently access with his or her github credentials
• a project can only be added once to the repository

Backend

• Create Project entity + model
• Create ProjectRepository
• Add Project array field for course entitiy
• Create get project autocomplete repository function
• Create add project to course repository function to course repository
• Create GetProjectAutocomplete Use Case
• Create AddProjectToCourse Use Case
• Link Use Case in routing

Frontend

• Create projects service
• Implement use cases in services
• Adapt data models
• Add courses form field for displaying repositories
• Implement dropdown autocomplete
• Implement validation

#4 #3

Expected Behavior:

• Browsing between projects will only show analyses for the current project.

Experienced Behavior:

• Analyses of previously called projects remain on page.

This feature will contain a list placed in the project settings, containing:

• the analysis name
• the analysis type (can be identical, in this case, only show name)

Backend steps:

• Implement GetAnalysesForRepositoryUseCase
• Link Everything up (GET course/courseId/projects/projectId/analyses)

Frontend steps:

• Create service method in project service
• Create AnalysesListComponent

Everything related to the management of authorized or owned courses.

This requires

• Define entities for Analysis structures (Datasources, Analyses etc.)

• Define repository for Analysises

• Define GetAnalysis Use Case (stub)

• Implement routing

• Implement repository cloning

This includes

• Adding a splash screen
• Adding Links, where they should be
• Fix the weird config behavior

Backend:

• Implement Use Case and Entities
• Embed seeance-core into backend
• Add Controller for Analyses
• Link to routing

The page must show

• The name of the project
• A link to github
• The associated course

It also has to check, whether the user is authorized to access the resource

• Implement Frontend Module
• Implement Frontend Component
• Add Router Link
• Add initialization logic etc.

#4

Backend Side

• Implement Visit Project Use Case
• Add recent projects array to user model
• Implement repo function
• Link everything up

Frontend Side

• Implement service call on project enter
• Implement "Recently Visited Grid" Component