Skip to content

Commit 3d815bd

Browse files
authored
Merge pull request #329 from Kaidama97/branch-dg-ug
Fix DG
2 parents af3ae87 + a56bce0 commit 3d815bd

File tree

2 files changed

+11
-9
lines changed

2 files changed

+11
-9
lines changed

docs/DeveloperGuide.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1124,13 +1124,15 @@ Users will be able to directly type `pref [index] [preference]`.
11241124

11251125

11261126
3. **Prevents accidental updates due to shifting list indexes after sorting**: <br>
1127-
**Current Issue**: After executing `pref save` for a person at a given index, the list re-sorts (by date, time and
1128-
last insertion), which might cause indexes to change. If the user tries to update the same person again using the
1129-
**previous index**, they may unintentionally modify a different person. This is not a bug but can lead to confusion and
1130-
incorrect updates. <br>
1131-
**Planned Enhancement**: We plan to improve the UX by making it clearer when the list has re-sorted after commands like
1132-
`pref save`. Possible solutions include displaying a message such as `List has been resorted. Please recheck indexes.`
1133-
or visually highlighting the recently updated person. This will help users avoid referencing outdated indexes.
1127+
**Current Issue**: After executing `pref save` or `edit` for a reservation at a given index, the list re-sorts
1128+
(by date, time and last insertion), which might cause indexes to change. If the user tries to update the same reservation
1129+
again using the
1130+
**previous index**, they may unintentionally modify a different reservation. This is not a bug but can lead to confusion and
1131+
incorrect updates. <br>
1132+
**Planned Enhancement**: We plan to improve the UX by making it clearer when the list has re-sorted after commands like
1133+
`pref save` or `edit`. Possible solutions include displaying a message such as
1134+
`List has been resorted. Please recheck indexes.`
1135+
or visually highlighting the recently updated reservation. This will help users avoid referencing outdated indexes.
11341136

11351137
4. **Enforce maximum number of occasions per reservation to 1**: <br>
11361138
**Current Issues**: ReserveMate currently allows users to input any number of `o/occasion` fields when adding a

docs/UserGuide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -151,7 +151,7 @@ The prefixes used in ReserveMate are universal across all commands.
151151
#### `p/` — Reservation Contact Number
152152

153153
- Phone numbers **must start with `8` or `9`** and be exactly 8 digits long (only Singapore phone numbers).
154-
- Multiple reservations can share the **same phone number** and **different date-time** — duplicates allowed.
154+
- Multiple reservations can share the **same phone number** and **different date-time**.
155155

156156
---
157157

@@ -160,7 +160,7 @@ The prefixes used in ReserveMate are universal across all commands.
160160
- Emails must match a **basic regex pattern**, but:
161161
- Technically valid emails may be **functionally incorrect** (e.g., `123@123`).
162162
- Strange but valid domains (e.g., `user@x-y.com`, `a@123.co`) are allowed.
163-
- Multiple reservations can share the **same email** and **different date-time** — duplicates allowed.
163+
- Multiple reservations can share the **same email** and **different date-time**.
164164

165165
---
166166

0 commit comments

Comments
 (0)