Я поговорил с разработчик о сборке.

Я поговорил с разработчик о сборке.
Сегодня он продолжает работу с базой данных, и у него возникли некоторые вопросы, ниже.

В понедельник мы сделаем слив и будем делать билд для предпоказа.
Мы постараемся подготовить билд и детализацию по дополнительным трудозатратам во вторник.

Вопросы:
- если мы регистрируемся с разных девайсов на один номер телефона, то сервер возвращает id одного и того же Driver
- чтобы получить профиль пользователя, нужно вызвать метод GET /app_secure/drivers/{driver_uuid}/profiles/{uuid}/, где uuid - это id профиля (откуда его брать - непонятно)
- есть еще метод GET /app_secure/drivers/{driver_uuid}/profiles/, который возвращает список профилей драйвера - сразу после регистрации этот список пустой. Почему список, тоже непонятно - может быть несколько профилей у драйвера? Тогда какой из них выбирать в конкретном случае?
- есть метод POST /app_secure/drivers/{driver_uuid}/profiles/, который создает новый профиль для драйвера, но при попытке вызвать его два раза, получаем ошибку от сервера (т.е. сервер дает создать только один профиль). Снова вопрос - зачем тогда список?

При текущем положении дел получается, что после регистрации нужно проверить список профилей и если он пустой, то создать новый профиль и использовать его. Если в списке уже есть профиль, то использовать его. А если, вдруг, их несколько, то какой тогда использовать?
В общем, текущая реализация выглядит костыльной - либо список излишен и в итоге должен быть просто один профиль на драйвера, либо не хватает какой-то информации.

Результаты (английский) 1:

I talked to the developer Assembly. Today, he continues to work with the database, and he had some issues below.On Monday we will drain and will do build for the pilot.We will try to prepare the build and detail additional work complete on Tuesday.Questions:If we register with different devices on a single phone number, the server returns the id of the same Driver-to obtain the user profile, you need to call the GET method/app_secure/drivers/{driver_uuid}/profiles/{uuid}/, where uuid is a profile id (where his take-wonder)-There are the GET method/app_secure/drivers/{driver_uuid}/profiles/, which returns the list of driver profiles-immediately after the registration of the list is empty. Why a list, too, wonder-multiple profiles may be the driver? Then which one to choose in case?-There are/app_secure/drivers/{driver_uuid}/profiles/POST method, which creates a new profile for the driver, but when I try to call it twice, you get an error from the server (i.e. the server gives you create only one profile). Again the question-why list?In the current situation, it turns out that after registration you need to check the Profiles list and if it is empty, then create a new profile and use it. If you already have a profile, then use it. And if, suddenly, there are more than one, then what is the use?In General, the current implementation of kostyl′noj list or looks like is superfluous and should eventually be just one profile to driver, or lacks some information.

Результаты (английский) 2:

I spoke with the developer of the assembly.
Today, he continues to work with the database, and he had some questions below. On Monday, we will make the sink and will do the build for predpokaza. We will try to prepare the build and detail of extra work on Tuesday. Questions: - if we are checking in with various devices to one phone number, the server returns the id of the same Driver - to get a profile, you need to call the GET / app_secure / drivers / {driver_uuid} / profiles / {uuid} /, where uuid - id of the profile (where to take it - is unclear) - there is a method of GET / app_secure / drivers / {driver_uuid} / profiles /, which returns a list of profiles driver - immediately after the registration list is empty. Why is the list, too, is unclear - there may be several profiles at the driver? Then some of them choose in a particular case? - There is a method POST / app_secure / drivers / {driver_uuid} / profiles /, which creates a new profile for the driver, but when I try to call him twice, we get an error from the server (ie the server It gives only create one profile). Again the question - why then the list? In the current situation it turns out that after registration you need to check the list of profiles, and if it is empty, then create a new profile and use it. If the list already has a profile, then use it. And if, by some chance, there are several, what if I use? In general, the current implementation looks spike - a list of superfluous and as a result should be a single profile on the driver, or is missing some information.

Результаты (английский) 3:

i talked to the developer of the building.
today he continues to work with the database, and he was having some issues below.

on monday we'll sink and do a build to предпоказа.
we will try to build and detail for additional трудозатратам tuesday.

:
- if we are checking in with different devices on one phone number, the server returns the id of one and the same driver.- to get a profile of the user, need to call the method get / app _ secure / drivers / {driver _ uuid} / profiles / {uuid} / where uuid is id profile (where his take is unclear)
- is another method of get / app _ secure / drivers / {driver _ uuid} / profiles /,which returns a list of profiles, the driver immediately after the registration of the list is empty. why the list too weird. - maybe a few profiles with the driver? then, which one to choose in a particular case?
a method of post / app _ secure / drivers / {driver _ uuid} / profiles /, which creates a new profile for the driver, but to call it twice, we get the error from the server (i.e. the server is to create only one profile).again the question - what list?

the current situation so that after registration need to check the list of profiles, and if it's empty, create a new profile and use it.if the list has a profile, then use it. if, then, there are several, what is the use?
in general.the current implementation is костыльной any list of superfluous and ultimately must be just one profile for the driver or missing some information.