matthieusb / shortcut-master-jhipster

Simple jhipster monolithic application to practise using your favorite Editors/IDEs shortcuts or even programming languages syntax.

shortcutmaster

This project is here to help you practise your favorite editor shortcuts and language syntax.

Installation

Coming soon

Contribute

If you wish to contribute and need to know how to use Jhipster for this project, please refer to the Developer instructions section of the wiki.

You can also find the Jhipster project official documentation here : http://www.jhipster.tech/documentation-archive/v4.14.0.

shortcut-master-jhipster's Issues

[Front] Training list : display a token to see which training is being followed by the current user

See if it is possible to add a little round token to the thumbnail for already followed trainings.

[Front] Simple exercise user interface

This will be the page where a user practises an exercises. For this simple version, the user should be able to :

• Start/Stop the exercise
• Choose several exercises modes : show (alwarus answer hint), hide (always hide), delay (show with delay)
• In started mode : Type in the shortcuts and see if they were right or wrong
• See a list of previously typed shortcuts below the input line (With right/wrong showed with green or red color codes)

[Front] Exercise training interface against an opponent

Take back the training interface of issue #33 and add an opponent

[Front] Remove entities modifications from simple user access

Remove the entry from the menu and prevent access to any kind of manual entity editing to a normal user.

Sonar Cloud integration

[Trans] Internationalize labels

Keystrokes labels are now stored in database only in english.
Leads to explore :

• Adding a table to store labels (and others things) for different languages
• Add this table row to the keystroke (for now, other tables could comme)

Normally, changing the front-end models would not be needed, except for the GET request who would feature a language header or info in body.

[Front] Administrator home page

Remove the default home page and display the different actions available for an administrator :

▶️ Use Bootstrap thumbnails to display each action available (See the main menu)
▶️ Keep the up menu as is, will be modified later to remove useless entries

[UPDATE] Jhipster 5 update

Use the sub generator

[Front] Screen with a training exercises list

The list should be display as a sucession or ordered exercies (No precise idea of how exactly)

Maybe use boxes and link them with arrows.

[Trans] Think about a training/exercise import feature

This would allow user to create/share their own collections of trainings and exercises.

Using it directly from users would be a bit harder though, maybe juste letting the admin import trainings through a file would be interesting.

[Front] Exercise list : display a token to see at which progression an exercise is

At the beginning, dummy token to simulate.

When opponent and test exercises are coded, will add the actual.

[Transversal] Modify README for project specificities

Current README is jhipster default (plus some icons linked to travis/sonar).

TODO -> Describe what to put in README

Travis CI integration

Add lombok support

Update services to match Impl

Some pre-generated services do not use and interface. Add an Interface and a ServiceImpl.

[Back] Endpoint to get a precise training exercises list

See issue #31 for target screen details

Get an exercises list with training id

[Front] Training list screen for users

The page should display all trainings available in the form of simple boxes containing the label of training.

All trainings should be separated by training type.

Reminder :

• Training type ▶️ Editor, IDE, Programming Language
• Training ▶️ Eclipse, Intellij, Pyhton, Bash

[Back] Endpoint to get training list

See issue #27 for details on the target screen.

Endpoint should return all available trainings without distinction.

Handle model impacts on frontend for Admin (TrainingFollowed, ExerciseVisited)

It should be possible to chosse a user in the UI.
Actions also have to be performed on backend.

Maybe a better way would be to create a real way for the admin to add new shortcuts.

Change spring boot banner

Current one is too big. Take a smaller ascii font

Finish implementing a basic model

Just the necessary entities :
Training (and its types + OS), exercises that have questions (Shortcuts or instructions) and opponents to play againt a user.

A user must be able to see which training he is currently involved into, and continue to the latest exercise they were working on.

We'll see later some gamification.

[Front] Cheatsheet of each training

The cheatsheet page should be accessible from the exercise list page and feature a list of all shortcuts/commands answers for each exercise (Separated vertically)

[BUG] Model rework needed

Check the tables and regenerate entities.

For example, keystroke has unneeded foregn keys. Maybe a ManyToMany is more appropriate in that case

[Front] Exercise final test interface

To be developed after #33 and #38 and their respective endpoints.

This is the final phase of an exercise progression. User shall answer successive questions and pass only when all answers are correct (not even one wrong answer accepted).

Generate entities and correct missing relationships

Add the relationships between user and TrainingVisited/ExerciseVIsited to User (jhi_user table). :

• Add to backend model
• Modify liquibase changelogs accordingly
• Modify angular model accordingly

[Back] Endpoint to get current user info for home page

See issue #29 for screen details

Endpoint should get all ongoing trainings and exercises to be able to compute progression on frontend.

[Back] Endpoint to store user training progression

Each training followed by a user should be stored so that it can be displayed and continued at its last exercise.

[Transversal] SQL Scripts to populate database with examples

This will be needed to easily test display at the beginning of our tests.

Maybe add a few things with manually through the admin console (Careful since some of the front CRUD parts of the interface are not all completely synced with the back-end manual modifications), and then extract the scripts through dbeaver/datagrip.

[Back] Endpoint to get exercise visited progression

See issue #31 for target screen details

This should allow use to know which exercise of current user and training has been finished or not

[Front] Home screen for normal user

Home screen for a normal user should display :

• A list of ongoing trainings with progression (see bootstrap progrss bar)
• Filter capabilities on : training type, name, (progress ?)
• Ordering by : alphabetical order, progress, (training type alphabetical order ?)

[Back] Endpoint to get exercise opponent

See issue #38

[Back] Endpoint to get info for a cheatsheet

See issue #43 for target screen details.

Should get all keystrokes and commands for the current training

SQL Scripts to ease liquibase modifications

Add sqll scripts to :

• Drop all tables in order of constraints
• Truncate all tables in order of constraints
• Dropt hibernate sequence

[Back] Endpoint to get training followed information

See issue #35 for target screen detail

Add this feature to the issue #28