pe's People
pe's Issues
Unnecessary requirement for user to indicate the minutes of the hour for availability
Posting certain comments can result in cOOPer requesting for unexpected results
Possible missing activation bar for `SignInDetailsParser`
Able to set avaibality for dates that have passed
Slight discrepancy between DG Manual Testing instructions for logging in and actual requirements for logging in
Very slight inconsistency in the capitalization of items in bulleted/numbered lists
Garbage input after a valid command is accepted
For example, entering list garbage input
will pass as a valid command in cOOper. This perhaps might be a part of the intended design (e.g. to allow for potential typos by the user) but it seems that this is not as consistent in some parts of the program. For example, when generating cf projections, garbage input after a valid input command (e.g. proj 5 garbageinput
) is not negelected:
After scheduling a meeting, availabilities remain unchanged
After a meeting is scheduled, it seems the case (and intuitively so) that both parties involved in the meeting will no longer be available on that particular date/time. However, their new availabilities after the meeting has been scheduled is not updated in the output using the availability
command. This might be confusing for users with even more meetings scheduled as it is difficult for them to identify the source of the conflicting schedule.
Possible missing return arrows for `Logging in` sequence diagram
There seem to be potential missing dotted line arrows for the sequence diagram for Logging in
. Even though the method calls might return void
, it seems like VerificationUi
should have a dotted-line returning back to :Login
for each method call made by :Login
.
Similarly, dotted line arrows from :Verifier
to :Login
seem to be missing after each Set
method call by :Login
in the alt
block.
If whitespace is entered before a command (`list`), program will not understand user input
Entering list
will print out the balance sheet as intended. However, if whitespace(s) are input before the command (e.g. in the event of a minor typo by the user), cOOPer is unable to understand the desired command input by the user:
The same applies to most, if not all, other inputs by the user as well (e.g. not able to accidentally add whitespace before input).
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.