Need to register and eventually pay (if there's lots of request)

Mettre en place des vérifications regex sur les différents champs des méthodes createBarController et userSignupController

Je ne comprends pas pourquoi mais même en passant l'id dans le body de la requête get, la réponse est toujours "couldn't retreive this bar".
D'ailleurs on a la même réponse si on ne fournit pas d'id, ce qui ne devrait pas être le cas.

Implement a way to verify email (send an email to the mail adress with a code or a link)

Create a request for bars in which we send the mail and password and get back the id and token

The workflow is to be determined but we can still implement the basic elements and pages.

This includes the textfield component and the form shape that can be found in the following image:

Pensez du front au back à la gestion des images

In the bars section of the main page when we deactivate the geolocation on the device it spins forever

Implement tests on the bar methods

Tout est dans le tire.
Une discussion/réflexion de groupe est nécessaire avant de se lancer.

You can create a random container decorated with a gradient and use InkWell to add splash color afterwards

Is your feature request related to a problem? Please describe.
No restrictions are currently in place to add code in the code base. This is dangerous

Describe the solution you'd like
Add restrictions of at least 1 CI github action validation + 1 peer review

Describe alternatives you've considered
Force documentation

Dans le createBarController, réfléchir à quels paramètres doivent réellement être obligatoires à la création (pas event par exemple)

Is your feature request related to a problem? Please describe.
We currently don't have any way to prove code regression if any. Indeed, no tests are made so one can clearly push code that's wrong and worse, breaks already existing code

Describe the solution you'd like
Adding a testing framework to the project and implementing it

Describe alternatives you've considered

• Manual testing: fine at first but unbearable afterwards

Additional context
Tests are automatically done now with github actions so it's really not a hassle to test the whole project

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe.
Currently no tests are being made before uploading.

Describe the solution you'd like
a test folder should be implemented in the src folder conainig all the tests files. We should use mocha as it is the most widely spread library.

Additional context
Putting it in CI would be a great idea

Créer un model (interface et schema) “adressBar” qui contiennent les champs [streetAdress: string; city: string;state:string;postalCode:number;country:string]
et utiliser ce schéma à la place de String pour stocker les adresses des bars

Is your feature request related to a problem? Please describe.
Separation could be done later on. Rn, it adds a lot of not needed issues for a project not yet live.

Describe the solution you'd like
A folder with all the routes and handlers

Il faut implémenter le QRcode

Explicite

Is your feature request related to a problem? Please describe.
We need a clean user crud api

Describe the solution you'd like
an api that respects the rest api convention given in https://hackernoon.com/restful-api-designing-guidelines-the-best-practices-60e1d954e7c9

Use this plugin https://alligator.io/flutter/geolocator-plugin/

Bars have different schedule depending on the day. And some days, they're closed

Il faudrait implémenter une page comme ca

Enregistrer la date de création des bars et des users (regarder l'objet mangoose Date, probablement approprié)

Ajouter un id pour les users et bars (trouver un moyen de les auto-générer)

Currently auth server is pretty shitty and basic. We should create a new workflow for it where:

• the user sends his phone and we add him directly in the database
• the user sends his code for the signup instead of "isPhoneConfirmed = true"
• then the rest is added to the db

Faire en sorte qu'on puisse modifier un bar et checker si ça met à jour le updatedAt (timestamp)

Trouver un moyen de stocker les heures et minutes pour les horaires d’ouverture et de fermeture des bars (il n’existe que l’objet Date et pas d’objet time dans mangoDB, donc il faudrait peut être créer un model “time” qui contiennent [hour:Number;minute:Number] )

Have in mind that bar have multiple pictures

delete what's not used

Add github actions

Short description

In order to automate some basic tests and prevent failing code to enter the codebase, we should add github actions as part of our integration process

TODO:

• Add github node action
• Add github dart action

qu'un bar puisse créer modifier supprimer un event et que tous les users puisse le voir

Il faut ajouter un champ password au model bar mais bien évidemment, comme pour les users, ne stocker que son hash