This repository has been archived by the owner on Jun 29, 2021. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 7
A guest or an authenticated user can list answers of a question #32
Labels
story
New feature
Comments
I want to do this one when the dependencies are ready :) |
@ana-lisboa I think all dependencies are ready :) |
I've started developing already ;)
Cumprimentos,
Ana Lisboa
A segunda, 26/10/2020, 10:08, Tiago Fernandes <[email protected]>
escreveu:
… @ana-lisboa <https://github.com/ana-lisboa> I think all dependencies are
ready :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC4HBOWBATJ656PWNBEGFQLSMVDDDANCNFSM4SC64NBA>
.
|
ana-lisboa
added a commit
to ana-lisboa/api
that referenced
this issue
Nov 1, 2020
ana-lisboa
added a commit
to ana-lisboa/api
that referenced
this issue
Nov 1, 2020
ana-lisboa
added a commit
to ana-lisboa/api
that referenced
this issue
Nov 1, 2020
ana-lisboa
added a commit
to ana-lisboa/api
that referenced
this issue
Nov 1, 2020
…tps://github.com/ana-lisboa/api into FEAT/laravel-portugal#32/GetAnswersFromAQuestion
ana-lisboa
added a commit
to ana-lisboa/api
that referenced
this issue
Nov 5, 2020
ana-lisboa
added a commit
to ana-lisboa/api
that referenced
this issue
Nov 8, 2020
ana-lisboa
added a commit
to ana-lisboa/api
that referenced
this issue
Nov 16, 2020
ana-lisboa
added a commit
to ana-lisboa/api
that referenced
this issue
Nov 17, 2020
ana-lisboa
added a commit
to ana-lisboa/api
that referenced
this issue
Nov 17, 2020
ana-lisboa
added a commit
to ana-lisboa/api
that referenced
this issue
Nov 22, 2020
josepostiga
pushed a commit
to ana-lisboa/api
that referenced
this issue
Nov 22, 2020
…estion # Conflicts: # CHANGELOG.md
josepostiga
pushed a commit
that referenced
this issue
Nov 22, 2020
… question (#53) * #32 gets answers from a question * #32 fix repeated route name * #32 code review improvements * #32 adds second round of code review * #32 adds minor code reviews * #32 adds final code review * #32 removes unneeded index * #32 edits changelog Co-authored-by: José Postiga <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Scenario
Given I'm a guest or an authenticated user of any type
When I send a GET request to /discussions/questions/{questionId}/answers
I expect to receive a list of paginated, non-deleted, answers resources (15 per page)
Given I'm a guest or an authenticated user of any type
When I send a GET request to /discussions/questions/{questionId}/answers with any searchable properties
I expect to receive a list of paginated, non-deleted, answers resources that match the query param (15 per page)
Given I'm a guest user
When I send more than 30 GET requests to /discussions/questions/{questionId}/answers within a single minute
I expect to receive a 429 Too Many Requests status code until the next minute
Searchable properties
author_id
: mapped to anauthor
query param (?author={id}
).created_at
: mapped to acreated[]
period type query param (?created[from]={start-period}&created[to]={end-period}
).Additional requirements
The list should be ordered from the most recent resources to the eldest.
This builds on the features of #25, which introduces the storage of questions resources.
The text was updated successfully, but these errors were encountered: