[TM-1677] Implement user verification BE

[Scriptmatico]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
• Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• Check the commit's or even all commits' message styles matches our requested structure.
• Check your code additions will fail neither code linting checks nor unit test.

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this introduce a breaking change?

• Yes
• No

Other information

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 8a9a0d8.

Command	Status	Duration	Result
nx run-many -t lint build	❌ Failed	34s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-02-21 16:56:02 UTC

[pachonjcl]

LGTM

[roguenet]

This userId should get a foreign key and this entity should get a relationship to user:

  @ForeignKey(() => User)
  @Column(BIGINT.UNSIGNED)
  userId: number;

  @BelongsTo(() => User)
  user: User | null;

[roguenet]

With the BelongsTo change requested on the verification entity, this can be a single DB query:

const verification = await Verification.findOne({
  where: { token }
  include: [{ association: "user", attributes: ["id", "uuid", "emailAddressVerifiedAt"]
});

if (verification?.user == null) throw new NotFoundException("Verification token invalid");

And then use verification.user below instead of user.