feat: empty string warning

[Keyrxng]

Resolves https://github.com/ubiquity/ts-template/issues/31

• Identifies empty strings and posts a comment onto the pull request
• updates that comment when changes are made
• removes it once all are fixed

QA: https://github.com/ubq-testing/bot-ai/pull/31

[github-actions[bot]]

Lines	Statements	Branches	Functions
	80% (4/5)	100% (0/0)	66.66% (2/3)

JUnit

Tests	Skipped	Failures	Errors	Time
1	0 :zzz:	0 :x:	0 :fire:	2.692s :stopwatch:

Coverage Report (80%)

File	% Stmts	% Branch	% Funcs	% Lines	Uncovered Line #s
All files	80	100	66.66	80
main.ts	80	100	66.66	80	9

[Keyrxng]

This was a mistake, meant to open it against my own dev branch and I don't have the option to close as unplanned lmao

[gentlementlegen]

@Keyrxng Just use this pull request as the final one, I converted it to a draft in the meantime.

[Keyrxng]

@FernandVEYRIER ready when you are mate

[ubiquity-os-deployer[bot]]

af57518

a61d62d

cdae93a

[Keyrxng]

• https://github.com/ubq-testing/bot-ai/pull/33#pullrequestreview-1957185580

• PR review comment for empty string

• Only empty strings added as part of the PR are commented on (pre-existing cannot be commented on)

[rndquu]

@Keyrxng Check this PR and this commit that assigns js variables empty strings.

The expected behaviour is that Empty string annotations should've been added, right?

[Keyrxng]

strange

it's identified the empty strings and their location and the GitHub UI is showing two comments but the comments are nowhere to be seen... any ideas why that might be off the top of your head? I'll see if I can debug the issue. I see it missed the one in static/main all together.

[rndquu]

any ideas why that might be off the top of your head?

Hard to say what went wrong