kendrewchan / pe Goto Github PK

I'm assuming the brackets [KEYWORDS] means they are optional, so there's incoherence between the first and second picture since both are supposed to represent optional keywords.

Message in UI does not include the capital case ones from UG.

The former picture Finding Properties Section does not have Command: find-p as it should, which I assumed is supposed to be standardised throughout, as seen in the latter picture.
Additionally, the former is not in point form, whilst the latter and most other sections are in point form.

Same as for buyers, unable to find by substring.
Imagine finding buyers/sellers of those with African names.

It was stated that names are not case sensitive, but I think they should be since they essentially represent the same thing. And can easily lead to many duplicates.

Same name could be allowed, since people with same name aren't really uncommon.

From what I've compared at least, most of the Command: details only show the command, but the former is incoherent with the rest

Overall GUI very laggy, takes 1-2 seconds just for any command to do anything.
More of a UX flaw in that sense.

Finding Asking Price greater than / > 1 trillion shouldn't be allowed, since the max Asking Price is 1 trillion, it always returns empty.

I'm assuming Seller is supposed to be on another line, but it isn't on another line in the above picture.

Price ceiling for properties at 1 trillion might be alittle too high?

As can be seen in UG, the former picture includes the capital case, but the latter does not. So a slight incoherence here.

Lack of space between whose attributes containany of the specified keywords.

As seen in point 3 of the first picture, the code is not highlighted, whereas the code in the second picture is highlighted.

Find seems to only find by words, not sure if it's intended but unable to find by substrings.
If someone has a really long name, like those African names, then it could be tough to type their entire name just to search for it.
Additionally, this seems to occur for all find commands as well, unsure if it was intended but even then, I think that searching by substrings is important.