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

As a contractor, I should be able to get all possible equipment types, so that I can assign one while creating an equipment entry #70

Open
arafaysaleem opened this issue Jul 25, 2021 · 0 comments
Labels
user story A brief explanation of a functionality or an interaction with the system, from a user's perspective

Comments

@arafaysaleem
Copy link
Contributor

Summary

As a contractor, I should be able to get all possible equipment types, so that I can assign one while creating an equipment entry.

Acceptance Criteria

GIVEN an contractor is requesting all possible equipment types in the desktop app
WHEN the app hits the /equipment/types endpoint with a valid GET request
THEN the app should receive a status 200
AND in the response, the following information should be returned:

  • headers
  • list of equipment types

Sample Request/Sample Response

headers: {
    error: 0,
    message: "..."
}
body: [
    {
        eq_type: "tools"
    },
    {
        eq_type: "machinery"
    },
    ....
]

Resources

  • Development URL: {Here goes a URL to the feature on development API}
  • Production URL: {Here goes a URL to the feature on production API}

Dev Notes

{Some complementary notes if necessary}

Testing Notes

{notes for QA, with examples if applicable}

@arafaysaleem arafaysaleem added the user story A brief explanation of a functionality or an interaction with the system, from a user's perspective label Jul 25, 2021
@arafaysaleem arafaysaleem mentioned this issue Jul 25, 2021
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user story A brief explanation of a functionality or an interaction with the system, from a user's perspective
Projects
None yet
Development

No branches or pull requests

1 participant