-
The arrows after "help" are not aligned properly.
![image.png](https://raw.githubusercontent.com/nus-cs2103-AY2425S1/pe/master/files/1ed2497c-16c7-464c-aad3-e2b2a06a48dd.png)
[original: nus-cs2…
-
## The ellipses might be misleading
## To Reproduce
Input an edit command with more than 1 `u/` prefix
## Expected behavior
According to the UG, we can have 0 or more university prefixes as suggeste…
-
![image.png](https://raw.githubusercontent.com/nus-cs2103-AY2425S1/pe/master/files/6c721e3a-cff4-4151-b3b3-0b6add3cfc4f.png)
The prefixes used are often truncated, such as p/, n/ and dr/. However, on…
-
While working on a file it randomly stopped working and I got this:
"Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/runpy.py", line 197,…
-
I've been trying to run the tool but can't find what format is expected in the `signer-config.local` settings 🤔
-
As written in the docs, NEASE only supports SE.MATS.JC.txt
- Question 1: Do we support SE.MATS.JCEC.txt as well?
- Question 2: Should we change the error message if any of the other outputs is used …
-
the ambiguous deadline format, indeed flexible but lacks of strict validation, can lead to inconsistent data entry and interpretation issue
![image.png](https://raw.githubusercontent.com/cxc0418/pe/ma…
-
There is an inconsistent command format. As shown below when using the /pu or pu/ markers.
As shown below it works in both cases.
![image.png](https://raw.githubusercontent.com/DarkDragoon2002/pe/ma…
-
The chosen parameter word "FEATURE_NAME" is quite confusing to the user, might be better to use KEYWORD. Also, this does not align with what is shown in the command window, which is PREFIX_NAME. Furth…
-
## tl;dr
SuperDB should support [YAML](https://yaml.org/) as an input/output format.
## Details
At the time this issue is being opened, super is at commit 222ded6.
Since SuperDB does not c…