Skip to content
This repository was archived by the owner on Dec 3, 2019. It is now read-only.
This repository was archived by the owner on Dec 3, 2019. It is now read-only.

Add API Documentation for Resources and Sessions endpoints #220

Closed

Description

@hpjaj

Feature

Why is this feature being added?

Our contributors need to be able to research, confirm and build against the API endpoints that the backend offers.

What should your feature do?

Document the following backend API endpoints in our online API documentation. When doing so, please follow the steps described in our README for how to document our API.

The endpoints to be documented are:

  • api/v1/resources_controller#destroy
  • api/v1/sessions_controller#create

Activity

  1. mindvoxel commented on Jan 2, 2018

    @mindvoxel

    @hpjaj I'm going to try to do this one, get to know the backend a bit better.

  2. hpjaj commented on Jan 2, 2018

    @hpjaj
    ContributorAuthor

    @christopher-wolff23 - it's yours!

  3. hpjaj commented on Jan 13, 2018

    @hpjaj
    ContributorAuthor

    @christopher-wolff23 - In case you're interested, here are a few closed PR's that are similar, that you can use for reference:

  4. mindvoxel commented on Jan 15, 2018

    @mindvoxel
  5. hpjaj commented on Feb 4, 2018

    @hpjaj
    ContributorAuthor

    @christopher-wolff23 - As there has not been a pull request, or any recent activity on this issue, we are assuming it has become abandoned. We are marking it available for other members to contribute.

    Here are our contributing guidelines which discuss the process and timelines for working an issue. You are more than welcome to re-reserve the issue, if it remains marked as "Status: Available"!

  6. mindvoxel commented on Feb 4, 2018

    @mindvoxel

    @hpjaj Sorry! I had some initial trouble wrapping my head around Rails, and then school started back up. Hopefully I'll find some time to look at it, again. But it's fine that you made it available.

  7. hpjaj commented on Feb 4, 2018

    @hpjaj
    ContributorAuthor

    @christopher-wolff23 - No worries!

  8. nagano564 commented on Mar 14, 2018

    @nagano564
    Contributor

    K... I will check this out on thursday to see if I have any shot of handling this. @hpjaj Let's see how it goes. If I can't figure it out I will just bug the crap out of my mentor.

  9. hpjaj commented on Mar 14, 2018

    @hpjaj
    ContributorAuthor

    @nagano564 - It's yours! Let me know if you run into any issues.

  10. hpjaj commented on Mar 21, 2018

    @hpjaj
    ContributorAuthor

    @nagano564 - Heads up, updated this story's acceptance criteria.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions