Bingo for meetings – part 3 – finalizing the “Create Meeting” scenario

Bingo

Bingo is a small project, written in TypeScript , and developed with Alexandru Badita in launch break (one hour - more or less). You can find sources at https://github.com/alexandru360/PresentationBingoCards/ . Those are my blog posts for Bingo : ( scroll below for the post)

Nr	Link
1	Create meeting
2	Create Tests
3	Finalize Create meeting
4	Sharing meeting
5	Keep Score
6	Add obsolete
7	Finalizing obsolete
8	End meeting
9	Dockerize tests
10	Azure CI tests
11	Yarn workspaces
12	CLI
13	Intermezzo - CLI improvements
14	typescript compile run with node
15	NestJS ,swagger and create a meeting
16	Finalizing API
17	Intermezzo - jest vs jasmine error
18	Refactor WebAPI and test service
19	Heroku Deploy NestJs
20	Angular
21	Deploy Angular to GitHub
22	WebAPI and Web
23	Documentation
24	Documentation of the code
25	Conclusions

In the “Create Meeting” scenario it was something that we have passed : ” application generates an unique Id that I can access the bingo cards ( state : not checked) for that meeting ” ( see https://github.com/alexandru360/PresentationBingoCards/projects/1#card-24165690 )
How we can emulate this ? Obviously, the meeting starts with a set of cards – but how about participants ? Do they have the same set of cards and check them ( bingo ) ?

There are some possible things to be programmed here:

1. The meeting have the unique set of cards and the dictionary of .

2. Every participant , when joining the meeting, have a copy ( by reference ) of the meeting cards and an array to see what is checked

3. Every card keep an array of participants that shows what participant have checked the card.

Guess what is easiear to implement ?

However, we have put a function on the meeting

public AllUnchecked(): boolean{
        return (this.Cards.filter(it=>it.IsChecked()).length === 0);
    }

and a test to ensure that, when creating a meeting, the function returns false.

So now the first scenario is done !

( On a personal note, I see that yarn is better than npm )