[PRJ-123] Server: extract class Foo
In the next commit, we're going to need to re-use the foo logic from
class Bar. Extract new class Foo from Bar to make it available for
re-use.
Second commit on the same ticket [PRJ-123] Server: use Foo in Baz
The users of BazClient need to be able to see foo information in the
baz dialog. Include Foo in the data sent by class Baz in the server.
Side note: the user might not even know that they are looking at Foo and Baz, it might be called something else in the UI they are shown. Whether or not this needs to be included in the commit message depends on the situation. [PRJ-456] Server: check ID for null in Foo
When class Foo was extracted from Bar in commit deadbeef ([PRJ-123]
Server: extract class Foo, 2026-06-06), a null check for the field
ID got lost by accident.
Check the field ID for null in class Foo to avoid a
NullPointerException when a foo event is sent to Baz.
>
> Summarizing it, 5/7 for delete have accounts, and 1/4 for keep have accounts. Not along after the final vote, a Wikipedia admin deleted the article. Being a little bit lax with my language, the majority's consensus agreed that Odin isn't notable, and the article had no reliable sources.
important clarification about a popular misconception: "Articles for deletion" discussions on English Wikipedia are not decided by vote.
For more details, see
- https://en.wikipedia.org/wiki/Wikipedia:Polling_is_not_a_sub...
- https://en.wikipedia.org/wiki/Wikipedia:Guide_to_deletion#Ov...