search

hippware / rn-chat

MIT License
5 stars 0 forks source link

Live Location Sharing - Baseline / API #3312

Closed bengtan closed 5 years ago

bengtan commented 5 years ago

This is the ticket to implement baseline and API functionality for Live Location Sharing (hippware/collaboration#5).

The server side ticket for the API is: New APIs for live location sharing (hippware/wocky#2146)

aksonov commented 5 years ago

@irfirl While I'm working on business logic (i.e. client-server communications), could you prepare dump (i.e. without touch handlers) React components for all mocks like you did before (using storyboard) ?

It will speed up things significantly

aksonov commented 5 years ago

@bengtan link to new API doesn't work

bengtan commented 5 years ago

@aksonov:

link to new API doesn't work

I've fixed the link, but it's a link to the server side ticket, not API documentation.

I'm not sure if there is dedicated documentation for the location sharing API (cc @toland). So if I unintentionally misled you, oops, sorry. Maybe try the graphl self documentation first?

aksonov commented 5 years ago

@bengtan Yes, GraphQL docs are quite self-explanatory, thanks...

bengtan commented 5 years ago

@aksonov:

If it's helpful to have this ticket split up a bit, ie.

  1. API and low level/wocky-client support, vs
  2. Baseline functionality and/or UI

or some other split, please let me know.

aksonov commented 5 years ago

@irfirl While I'm working on business logic (i.e. client-server communications), could you prepare dump (i.e. without touch handlers) React components for all mocks like you did before (using storyboard) ? It will speed up things significantly

@irfirl Alan, could you respond?

aksonov commented 5 years ago

@bengtan Yes, we can split it as you suggested - API/Baseline (this ticket) and probably several tickets for UI (one ticket per mock)

irfirl commented 5 years ago

@aksonov yes I can work on that

bengtan commented 5 years ago

I've split out a bunch of tickets. See the parent Epic.

Also, I'm going to close this as 'Not QA-able'. It would be easier/simpler for QA to verify the UI tickets instead of directly verifying this one.

aksonov commented 5 years ago

@irfirl Great, please assign to yourself tickets you are working on to avoid double work and intersection