benclmnt / pe Goto Github PK

To Reproduce

Steps to reproduce the behavior:

1. Open the review mode
2. Try to enter command in the main mode command box

Expected behavior

I should be able to type in commands,

Screenshots

No details provided.

Describe the bug

There is no way for the user to close the help popup without using a mouse

To Reproduce

Steps to reproduce the behavior:

1. Enter help command

Expected behavior

Perhaps it is nice if we can use ESC key to close the help popup

To Reproduce

Steps to reproduce the behavior:

1. Enter help command
2. Minimize help popup
3. Enter help command again

Expected behavior

Help popup show up on top, everytime help is called

No details provided.

It is also unclear what makes a card unique.

Screenshots

Evidence

It is only mentioned once and in page 44 / 69 of the UG. It is very very hard for the user to be aware of this gotcha. I am only aware of this after reading the DG. 😢

Suggestion

Perhaps add this warning in the quick start or FAQ?

And make it bigger or use a warning box to catch user's attention?

No details provided.

Not sure which one is right, but perhaps the team could settle on one

No details provided.

To Reproduce

Steps to reproduce the behavior:

1. Change economics -> economic
2. Open flashnotes

Expected behavior

Show up as a new deck

Screenshots

To Reproduce

Steps to reproduce the behavior:

1. At the end of a review session, entering help commands return an error

Expected behavior

Help command should still work

Screenshots

Describe the bug

Review Pane blocks all other application and it cannot be minimized without losing the progress. It is inconvenient to have to move the pane all around

To Reproduce

Steps to reproduce the behavior:

1. open Review mode
2. try to minimize

Expected behavior

Review pane should be able to be minimized, if user wanted to see other application.

Screenshots

I think the use case should resume at step 1 in this case.

Screenshots

To Reproduce

Steps to reproduce the behavior:

1. Open review mode
2. Press enter, flash notes will show suggestion to open help
3. enter help
4. Get second picture (which is expected)
5. go until all review questions is answered
6. Repeat step 2 - 3
7. Get the third picture instead

Expected behavior

Open help should be the same for consistency,

Screenshots

Evidence

Page 4 -5 , under Architecture section, the team included a Logic Class Diagram, which is then repeated again below.

Suggestion

Perhaps it is better to just have the diagram in one place, since it is confusing for the reader to meet the same diagram twice. Additionally, personally I think it didn't really add much value to have the Logic Class Diagram under the Architecture section, but maybe its just me.

No details provided.

To Reproduce

Steps to reproduce the behavior:

1. Change the name of flashcards to flashcard in flashnotes.json. Only a blank screen is shown. Upon checking, all my data is gone.

Expected behavior

Show a message to the user

Do not directly erase all user's data, since it is hard for user to create all flashcards again by hand.

Screenshots

This feature is not optimized for CLI users, since I cannot use left and right key to edit my command halfway

Steps to reproduce the behavior:

1. Enter a command halfway
2. Switch to a different application (in my case pdf)
3. Go back to flashnotes (using Alt-Tab). Do not use mouse to click on the command box or anything
4. Try left and right key, and it will just move between file and help option

Screenshots:

I cannot provide a video sadly :(

I'm not sure if this is just a documentation bug, or a functionality bug

To Reproduce

Steps to reproduce the behavior:

1. Enter deck economics
2. Add card with questions economic and answer econ
3. Add card with questions economic and answer lit
4. change tag of the card in step 3 to lit
5. find econ only returns the first

Expected behavior

Find returns all cards with matching questions

Screenshots

In this module, I believe we are not supposed to include the condition inside a branch component.

I think the usecase should resume at step 1 in this case.

Screenshots

I think the use case should resume at step 1 in this case.