Skip to content
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.

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

Define Acceptance criteria for font-end team #1

Open
Troush opened this issue Jul 17, 2017 · 1 comment
Open

Define Acceptance criteria for font-end team #1

Troush opened this issue Jul 17, 2017 · 1 comment

Comments

@Troush
Copy link
Member

Troush commented Jul 17, 2017

\cc @Nebo15/front-end

@alexeybondarenko
Copy link

alexeybondarenko commented Jul 17, 2017

A common situation for FE is that we need to show a list of the items. To make search process simple we define filters and search fields.

I propose to define by default query parameters regards to this principles:

  • if a property is an enum - use a full match of values that are split with a comma. (eg, access_token,refresh_token.
  • if a property is a text - use a LIKE search. We will use it for search in selects and search filters in list views
  • if an entity has a foreign key - accept the ids of the related entities (eg. settlement_id as query parameters for a search of the streets). 172eea1a-33d6-41d4-af82-4b1c364a911b,cd683d1b-e4f7-429f-a454-1a6c7312bbbf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants