v1.4

What's Changed

• Fix website name by @ReflectiveObsidian in #202
• Add clearer font by @DingBao-sys in #203
• Update minor errors in user guide by @Tsenrae in #215
• Attribute mega update by @Bandov in #265
• Update UG (PE-D feedback) by @ReflectiveObsidian in #269
• Fix relationship command bugs by @Emberlynn-Loo in #270
• test codecov by @Bandov in #271
• Bug with invalid relationtypes with s by @Emberlynn-Loo in #277
• Fix relationship bugs by @Tsenrae in #279
• Delete feature change by @Emberlynn-Loo in #281
• Sex attribute fix by @Bandov in #278
• fixed addperson by @Bandov in #283
• Make it so person can't be a brother and a sister etc. by @Emberlynn-Loo in #284
• Fix bugs with loading data when editing the json file by @Tsenrae in #288
• Update ug part 2 by @ReflectiveObsidian in #292
• fixed the error message by @Bandov in #293
• Fix error in gender relationships by @Emberlynn-Loo in #295
• DG update for attribute and person by @Bandov in #298
• Update Model(relationship portion) of DG. by @Tsenrae in #299
• Fix bug with loading data when editing json file by @Tsenrae in #296
• Attribute relationship gender by @Emberlynn-Loo in #303
• Update DG Appendix: Requirements portion by @Tsenrae in #305
• Repackage relationship classes by @Emberlynn-Loo in #306
• Dg feature implementation by @Bandov in #308
• Update loading of data to ensure that sex attribute gender matches with gender of relationship roles by @Tsenrae in #307
• Improve code quality for UI by @DingBao-sys in #310
• Dg update by @Bandov in #312
• attempt to fix the toc by @Bandov in #313
• fixed the errror of deadlinks by @Bandov in #314
• Add the editRelationship and deleteRelationship feature implementations to DG by @Tsenrae in #309
• Update DG syntax and organisation by @Tsenrae in #316
• Add anySearch implementation to DG by @Tsenrae in #317
• Add Updated UI architecture diagram by @DingBao-sys in #315
• DG for addRelationship Command by @Emberlynn-Loo in #320
• Relationship code quality by @Emberlynn-Loo in #319
• Improve code quality for saving features by @Tsenrae in #318
• Ug toning update by @Bandov in #323
• Fix ug box by @Bandov in #324
• change block to span by @Bandov in #325
• fixed the dialog box by @Bandov in #326
• fix bugs by @Bandov in #327
• Ug branch by @DingBao-sys in #328
• Fix UG by @DingBao-sys in #332
• Add implementation text for person commands by @ReflectiveObsidian in #322
• U gbranch by @DingBao-sys in #333
• Ug v3.0 by @Bandov in #334
• Remove extra destroy model indicator in DG by @ReflectiveObsidian in #330
• addded personality to UG by @Bandov in #335
• more PERSONALITY by @Bandov in #336
• Dg v2.0 by @Bandov in #337
• Add planned enhancements for relationships to DG by @Tsenrae in #339
• complete UG by @DingBao-sys in #338
• Add back to table for every section by @DingBao-sys in #340
• Add before/after images for all relationship features by @Tsenrae in #341
• update the UG by @Emberlynn-Loo in #342
• Ug figures update by @Bandov in #343
• changed all figures to use figcaption by @Bandov in #344
• Dg update by @DingBao-sys in #345
• done by @DingBao-sys in #346
• Ug image update by @Bandov in #347
• Ugdg updates by @Bandov in #348
• Add constraints for relationships in UG (warnings and notes) by @Tsenrae in #349
• Update syntax by @Tsenrae in #350
• Update relationship constraints by @Tsenrae in #351
• Update UG by @Tsenrae in #352
• fix links and edit file issue by @Bandov in #353
• update Ug by @Emberlynn-Loo in #354
• fix image by @Bandov in #355
• fix lijnks dg by @Bandov in #356
• Update DG by @Tsenrae in #358
• Final ug branch by @DingBao-sys in #357
• update ug by @Emberlynn-Loo in #359
• ug update by @Emberlynn-Loo in #360
• page update by @Emberlynn-Loo in #361
• update by @Emberlynn-Loo in #362
• update ug by @Emberlynn-Loo in #363
• Fix DG wording issues by @ReflectiveObsidian in #364
• Update UG by @Tsenrae in #365
• update ug by @Emberlynn-Loo in #366
• update-ug by @Emberlynn-Loo in #367
• Fix edit relationship invalid command format message by @Tsenrae in #368
• update c.10 by @Bandov in #369
• update by @Emberlynn-Loo in #370
• master by @Bandov in #371
• ug update by @Emberlynn-Loo in #372
• ug-change by @Emberlynn-Loo in #373
• update ug by @Emberlynn-Loo in #374
• fix ug by @Emberlynn-Loo in #375
• update DG by @Bandov in #376
• fix ug by @Emberlynn-Loo in #377
• fix ug by @Emberlynn-Loo in #378

Full Changelog: v1.3...v1.4

v1.3

Release notes

• Edited AnySearch to Return ResultContainer containing information for… by @DingBao-sys in #121
• Main window design branch by @DingBao-sys in #122
• fix UI bugs by @DingBao-sys in #123
• Minor UI bugs by @DingBao-sys in #124
• UI by @DingBao-sys in #125
• Main window design branch by @DingBao-sys in #127
• Main window design branch by @DingBao-sys in #129
• Update familySearch command to work with new UI by @Tsenrae in #130
• Main window design branch by @DingBao-sys in #131
• checkstyle by @DingBao-sys in #132
• Fix delete relation type bug by @Emberlynn-Loo in #126
• fix Ui bugs by @DingBao-sys in #133
• Command line box design by @DingBao-sys in #135
• Finalise CLI design by @DingBao-sys in #136
• checkstyle by @DingBao-sys in #137
• made all commands non case sensitive by @Bandov in #138
• Final UI desgin by @DingBao-sys in #139
• Find UUID feature by @Bandov in #148
• deleted email attribute and refactored test code by @Bandov in #149
• Deprecate Name, Phone and Address and update test cases to reflect new changes by @Tsenrae in #151
• fix compressing dialong box by @DingBao-sys in #155
• Deprecate ArgumentMultimap by @ReflectiveObsidian in #157
• Dg update by @ReflectiveObsidian in #156
• Fix relationship flaws by @Emberlynn-Loo in #160
• Update saving to include rolelessDescriptors and roleBasedDescriptors in Json format by @Tsenrae in #169
• Update user guide to match latest version v1.3 by @Tsenrae in #168
• Tell user what to do when they enter an invalid command by @ReflectiveObsidian in #173
• set Minresolution by @DingBao-sys in #175
• Fix add errors by @Emberlynn-Loo in #174
• Deprecate UI element classes by @ReflectiveObsidian in #161
• made find able to parse phrases and words instead of just finding words by @Bandov in #176
• Update AddRelationshipCommand to include checks for number of bioParents relationships (cannot be more than 2) by @Tsenrae in #177
• Update UG by @ReflectiveObsidian in #178
• Update clear address book to also clear all added relationship descriptors (role-based and roleless) by @Tsenrae in #179
• fix delete feature bug by @Bandov in #180
• Update front page of website by @Tsenrae in #182
• Fix bugs relationship by @Emberlynn-Loo in #181
• Update command strings by @ReflectiveObsidian in #184
• Capitalize attribute names by @ReflectiveObsidian in #185
• Change clear terminal command from "clr" to "c"/"clear" by @ReflectiveObsidian in #171
• Rename jar file to Gene-nie.jar by @ReflectiveObsidian in #187
• Cli bug branch by @DingBao-sys in #183
• correct images filepath by @DingBao-sys in #188
• Make attributes case-insensitive by @ReflectiveObsidian in #186
• more stable UI for jar release by @DingBao-sys in #192
• Revert deleteAttribute to returning void instead of bool by @ReflectiveObsidian in #189
• Update final user guide changes for v1.3 by @Tsenrae in #195
• updated User Guide and made attribute names uniform by @Bandov in #191
• Improve addrelationship error message by @ReflectiveObsidian in #198
• improve add command errors by @ReflectiveObsidian in #194
• Improve delete behaviour by @ReflectiveObsidian in #197
• Update UG syntax error by @Tsenrae in #199
• Improve find command by @ReflectiveObsidian in #200
• Make edit attribute command parser same logic as add attribute command by @ReflectiveObsidian in #201

Full Changelog: v1.3a...v1.3

v1.3a

Release Notes

New Features
Multi-Attribute Addition
You can now add multiple attributes to a person in a single command. The command format is:
add /UUID /attributeName1 attributeValue1 /attributeName2 attributeValue2 ...
For example, to add a name and phone number to a person with UUID 123, you would use:
add /123 /Name John Doe /Phone 12345678

Multi-Attribute Deletion
You can now delete multiple attributes from a person in a single command. The command format is:
delete /UUID /attributeName1 /attributeName2 ...
For example, to delete the name and phone number from a person with UUID 123, you would use:
delete /123 /Name /Phone

Multi-Attribute Editing
You can now edit multiple attributes of a person in a single command. The command format is:
editAttribute /UUID /attributeName1 attributeValue1 /attributeName2 attributeValue2 ...
For example, to edit the name and phone number of a person with UUID 123, you would use:
editAttribute /123 /Name Jane Doe /Phone 87654321
Please note that the attribute must exist before it can be edited. If the attribute does not exist, an error message will be displayed.

Bug Fixes
Fixed a bug where the deleteAttribute command was only deleting one attribute at a time. It now correctly deletes all specified attributes.
Fixed a bug where the deleteAttribute command was not correctly parsing the UUID from the command. It now correctly parses the UUID and attribute names from the command.

Improvements
Refactored the AttributeUtil class to include a method that creates an Attribute object from a given attribute name and value. This method is now used in the AddCommand, DeleteAttributeCommand, and EditAttributeCommand classes to create the Attribute objects, centralizing the attribute creation logic and making the code more maintainable.

v1.2

JENGA

Attributes

Addition of attribute Pet with value dog

Add Attribute Command: This command allows users to add attributes to a person in the address book. The command format is addAttribute \uuid <uuid> \<attributeName> <attributeValue>. The uuid is the unique identifier of the person, attributeName is the name of the attribute to be added, and attributeValue is the value of the attribute.

Deletion of attribute Address

Delete Attribute Command: This command allows users to delete attributes from a person in the address book. The command format is deleteAttribute \uuid <uuid> \<attributeName>. The uuid is the unique identifier of the person, and attributeName is the name of the attribute to be deleted.

Persons

UUID for Person: Each person now has a unique identifier (UUID), which can be used to uniquely identify a person in the address book.

Attribute Management: The Person class now supports managing attributes of a person. This includes adding, updating, and deleting attributes. Attributes are stored in a HashMap, allowing for efficient access and modification.

Attribute Retrieval: The Person class provides methods to retrieve a person's attributes by their name.

Relationships

Screen.Recording.2024-03-22.at.11.37.29.AM.mov

Addition of relationship between users 10cb and 6fd4 of type Friend

Add Relationship Command: This command allows users to add relationships to two persons in the address book. The command format is addRelation <uuid1> <uuid2> <relationType>. The uuid is the unique identifier of a person, thus uuid1 and uuid2 belong to two people respectively. relationType is the type of the relationship between the two people to be added. As of now, relationType only supports friend and family but two people can be friend and family at the same time.

editRelation.mov

Editing of relationship between users 10cb and 6fd4 from type Friend to Family

Edit Relationship Command: This command allows users to edit a relationship between two persons in the address book. The command format is editRelation <uuid1> <uuid2> <oldRelationType> <newRelationType>. The uuid is the unique identifier of a person, thus uuid1 and uuid2 belong to two people respectively. oldRelationType (eg. family) is the name of the previous relationType to be edited from (eg. to friend). newRelationType is the name of the new relationType (eg. to friend) to be edited to (eg. from family). As of now, both relationTypes only support friend and family but two people can be friend and family at the same time.

DeleteRelation.mov

Deletion of relationship between users 10cb and 6fd4 from type Friend to Family

Delete Relationship Command: This command allows users to delete relationships from two persons in the address book. The command format is deleteRelation <uuid1> <uuid2> <relationType>. The uuid is the unique identifier of a person, thus uuid1 and uuid2 belong to two people respectively. relationType is the type of the relationship between the two people to be deleted. As of now, relationType only supports friend and family but two people can be friend and family at the same time.

Saving

Exit Command (Saving): This command allows users to exit the program and will save their current addressbook. It has been updated to handle saving of persons together with their individually inputted attributes and relationships.