Known Issue: Instances where `mongoose-unique-validator` package causes incorrect error thrown involving `_id` must be unique error

[JonathanLeeWH]

Known Issue:

Instances where mongoose-unique-validator npm package causes incorrect error thrown involving _id must be unique error. It is an ongoing issue in mongoose-unique-validator npm package.

Affects

It affects frontend integration where bad requests status code 400 would be shown for adding or editing software as it will shown software as not added successfully.

Potential Workaround:

• To remove the mongoose-unique-validator plugin entirely and check the error code thrown by mongoose manually.
  or
• To wait for a bug fix in mongoose-unique-validator plugin.

The stopgap measure:

• Whenever the demo software repository website is to be demo, best to use a new mongodb database. (Not feasible in long run but a temporary measure for showing functionality in demonstration)
• To downgrade mongoose-unique-validator to last known working version (PR Temporary Solution to Issue #272: mongoose-unique-validator downgraded to 2.0.3 #301 and Amend firebase private key decode from base64 #302) [A temporary measure and not a long term solution due to long term security concern]

Related Issue:

mongoose-unique-validator GitHub

GitHub Issue 1
GitHub Issue 2

[JonathanLeeWH]

• Temporary Solution: mongoose-unique-validator downgraded to last working version 2.0.3 with npm install mongoose-unique-validator@2.0.3 --legacy-peer-deps
• Temporary added --legacy-peer-deps flag to npm install in Dockerfile and Dockerfile-ci to support the downgraded mongoose-unique-validator 2.0.3