Skip to content

Issues: tomo-app/tomo_api

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

35 Open 38 Closed
35 Open 38 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Create edit user language mutation and don't allow for duplicate user langs and fluency levels api backend
#102 opened Feb 16, 2021 by leahriffell
Creating a blocked pairing cancels any future pairings that already exist between those users api backend blocked pairings
#96 opened Feb 14, 2021 by leahriffell
Error handling for creating a new availability when user doesn't have target and native languages set api backend testing
#88 opened Feb 7, 2021 by leahriffell
Look into: when updating a user's target or native language, it finds based on fluency level but user could have more than 1 target and native api backend
#87 opened Feb 7, 2021 by leahriffell
Refactor Topic model's translations_for_languages method to allow for any num languages api backend refactor
#81 opened Feb 5, 2021 by leahriffell
As a user, I can submit application feedback to the developers.
#80 opened Feb 4, 2021 by leahriffell
getPairings query can pass in optional filter for cancelled true/false api backend
#77 opened Feb 4, 2021 by leahriffell
Date / datetime should be consistent across all types (ex: availabilities and pairings) api backend
#75 opened Feb 4, 2021 by leahriffell
When a user is cancelled on (other user cancelled pairing), try and create a new pairing if availability exists backend
#72 opened Feb 4, 2021 by leahriffell
Figure out how to measure test coverage for the FE
#66 opened Feb 1, 2021 by leahriffell
Create test or staging API for FE to use in testing api backend testing
#65 opened Jan 30, 2021 by leahriffell
Require API token for any non-authorization required requests api backend
#63 opened Jan 28, 2021 by leahriffell
@leahriffell
Client must have API key to hit BE endpoint api backend
#62 opened Jan 19, 2021 by leahriffell
Add user's languages to the getUser query api backend MVP
#59 opened Jan 1, 2021 by leahriffell
Use more clear namespacing format in tests
#52 opened Dec 26, 2020 by leahriffell
Create updatePassword mutation api backend
#49 opened Dec 26, 2020 by leahriffell
Research graphql input types (types > input) api backend spike
#48 opened Dec 23, 2020 by leahriffell
Add logic that user's availability's end date time must come later than start date time backend
#45 opened Dec 23, 2020 by leahriffell
@leahriffell
Create pairing functionality api backend
#44 opened Dec 23, 2020 by leahriffell
Create BlockedPairings delete mutation api backend blocked pairings
#43 opened Dec 23, 2020 by leahriffell
1 task
Create getFutureAvailabilities by user and status query api backend
#39 opened Dec 23, 2020 by leahriffell
Reorganize GraphQL queries folder
#35 opened Dec 21, 2020 by leahriffell
Enforce secure password backend
#34 opened Dec 18, 2020 by leahriffell
Create 'Incidents' migration, model and test backend database
#29 opened Dec 17, 2020 by leahriffell
TopicTranslations mutations and queries api backend MVP
#25 opened Dec 16, 2020 by lkriffell
3 tasks
MVP Mutations/Queries
ProTip! Exclude everything labeled bug with -label:bug.