tim-siu / pe Goto Github PK

This causes inconvenience for people trying to see source code.

According to the text book:
Case sensitivity: In general, case sensitivity of something should follow the case sensitivity of the real world entity it represents e.g., as person names are not case-sensitive in the real world, they shouldn't be case-sensitive in the app either. The same applies for search keywords. Incorrect case sensitivity can be considered a FeatureFlaw.

It will be helpful if constraints for User name is mentioned. Otherwise, users have to figure this out by trail and error.

For example, "abc s/o abc" is not allowed when inputting the name. This can cause inconvenience as "s/o" is common in people's legal name.

Also, pure numeric names are allowed, which may not be intended.

For example, 1a1 should has an indention level deeper.

It may be better if the screenshot is placed under the text and smaller.

The specific command file should not be mentioned in use cases ad it belongs to implementation details.

Unhashed passwords can be easily retrieved and data is not encrypted either. It appears that the feature may need further polishment.


This may cause confusion to users.



It seems like there are missing exception handling. There appears to be some documentation in planned enhancements. Since this is a functionality bug, I believe such issues can still be reported.

Using ref frames may be appreciated.