simaob/posso-ir-api

Allowing people to track the state of queues to supermarkets, pharmacies, and other places. To avoid crowds in a time where self-isolation is key. #stayhome!

Hi there 👋

posso-ir-api's Issues

Criar importer das lojas

Implementar JWT

Update sign up page to present the user with two possible routes

Currently when users access the sign up page they can only register as Collaborators. To improve store owner engagement we want to change this page to present two routes to the users: Collaborator and Store Owner;

We could do this by just enabling the role dropdown to be used by the users, but to I'm wondering if it might be nicer to have an initial step where we present the two possibilities to users and what each of them allows them to do, see the sketch with my idea.

This adds an extra step, but it allows users to know what they are registering to do. And makes the register forms a little more simple as we don't need to check the value of the role chosen and change things based on that.

For the store owners form we need to allow the users to pick the stores they want to manage, as we already have, or in a nicer element, but we need to ensure that this connection is not active until we validate it. So we need to add a state to the user_stores table.

With this said, I'm now wondering if we really want to be validating all the store owners that might appear by us opening this up... thoughts?

List of (potential) tasks

• Update register page to allow the two paths;
• Move the current collaborator sign up to a separate route;
• Create a new store owner sign up page with the possibility of selecting stores to manage;
• Ensure that stores assigned to newly created store owners are not immediately available for them to report on, these need to be approved;
• Email presence needs to be mandatory for Store Owners

endpoint para ver o estado de um supermercado

verbo: GET
parametro: id do supermercado

As an API client I want to receive only the 100 closest stores from where I am located

Currently the /api/v1/stores?filter[location]=lat,long request will return up to 300 stores that are in a 5km radius from the provided lat long. This is a bit overwhelming for the applications to handle and probably to much for the users to parse through. So we are thinking of reducing the size of the response and return only the 100 stores that are close to the provided location.

If the user wants to see more locations they could move the map around and request for a slightly different location.

There are some potential concerns with discoverability, as in very populated places the users might not get the full list of stores. Some options are for the application to pass the store_type filter to the backend, for us to play a bit with the total number of stores returned, or in a future iteration paginate the results.

For now let's go with the backend change alone.

Configure cdn to store the information of the stores

The stores won't change frequently, so it would be great to have the requests in cdn,

Endpoint para pesquisa de supermercados perto de uma localização

verbo: GET
parametros: georeferenciação/coordenadas

Install redis

Install redis and make the jsonapi resources use it

adicionar JWT para autenticação

Implementar oAuth

Update home page to explain what is it about, how can people use the app and how they can contribute

Currently we have a beautiful welcome message and when logged in as an admin there is a dashboard with some metrics, we should update this to explain a bit what this site is about and how can people use the application and contribute to it:

• as users of the app;
• as collaborators for data additions and editing;
• as store owners managing their stores and reporting on their stores queues;

There are no designs for this, so whoever picks it up can come up with something. We are using TwitterBootstrap so maybe using some cards and some images or just some cards with text might be good. Don't forget that it needs to be localised and we can get translations from some of the other volunteers.

Criar um endpoint para fazer o registo de interesse em ir a um supermercado

verbo: POST
enviar: id supermercado, id do user/authorização, quando:timestamp, estimativa_da_visita:tempo em minutos

Update routes to set the app locale depending on the domain used.

We have the following subdomains set up, and we should set the default locale of each of them based on the domain;

• api.posso-ir.com -> pt
• api.puedo-ir.es -> es
• api.can-i-go.co.uk -> en
• api.necakajvrade.com -> sk

Criar endpoint para registar a lotação do supermercado no momento

verbo: POST
parametros: id do supermercado, valor: [vazio, médio, cheio ou percentagem], authenticação

Enable emailing system so that users can use the Forgot your password? feature

Improve the calculation of the status

It's not optimized at all, and it should cause it's accessed frequently.