Skip to content

Conversation

@MaksimHolubeu
Copy link

1.  task check
{
  courses(filters: {published: true})
  {
    id
    published
    title
  }
}
2. task check
{
  collections {
    id
    title
    courses {
      id
    }
  }
}
3. task check
{
  includes(collection: 1, course: 13)
}
4. task check
{
  courses(filters: {published: true})
  {
    id
    published
    title
    discount
  }
}
5. task check
mutation {
createCourse(input: {title: "The Test",
  description: "desc",
  published: true, collections: [5,6]}) {
    id
    title
    description
    published
    discount
}
}

    1. To extend the courses API to accept a 'published' argument that controls
       whether or not published courses are returned.
    2. Use Service object - to extend future task easly
    3. Try write in one file, and think that it incorrect.
    1. To add a GraphQL API for returning collections along with their associated courses.
    2. Use Service object - to extend future task easly
    3. Try write in one file, and think that it incorrect.
    1. The consumer of the API now needs to know something specific:
    whether a given course is a member of a collection or not.
    Extend the API to allow the consumer to determine whether a given course, referenced by its ID, belongs to a
    particular collection.
    2. Simple implementation, not need split to files
    3. Split to files
    1. Add display the percentage discount alongside the
       courses. As a course could have multiple discounts, ensure that the largest
       possible discount is returned for each course.
    2. Add field discount
    3. -
    1. Add publish courses via the API. Implement a
       GraphQL mutation to accomplish this.
    2. Add mutation and service for create course
    3. -
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

Successfully merging this pull request may close these issues.

1 participant