tioluwani94/customer-success-app issues and pull requests

#20 - Use the reducer pattern in accounting for the data context when creating a provider

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: Application

#19 - Create two different networks adapter that account for the following scenarios

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: Application

#18 - Using Json server, create a mock api-call to send down the list of entities (bookings, clients, tutors, etc)

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: BookingListPage, ClientListPage, TutorListPage

#17 - The logic to implement the server side search. When no result is found, just display no result found.

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: BookingListPage, ClientListPage, TutorListPage

#16 - The worked on bookings would be stored in the provider. The format includes just an array of the booking orders.

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: BookingListPage

#15 - Design the Tutor Item Component. This consist of the name and the email.

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: TutorListPage

#14 - Design the Tutor list component as well as the search. [should also account for client and server search]

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: TutorListPage

#13 - Endpoint to fetch the list of tutors. using json-server and accounting for the search functionality also

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: TutorListPage

#12 - Design the Client List Item Page. this consist of the name of the client, the email and the phone number of the client.

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: ClientListPage

#11 - Design the Client List Page and the Search bar which accounts for both client and server search

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: ClientListPage

#10 - Endpoint to implement the fetching of client data.

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: ClientListPage

#9 - the logic to implement the server side filtering. This doesn't consider when there is an array of worked bookings.

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: BookingListPage

#8 - The Logic to implement the Client side search. If there is no result, the default text that shows when the result is empty also suggest to check the server for the data. Clicking on the suggestion changes the checkbox state to server.

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: BookingListPage

#7 - The logic to implement Client side filtering for the following

Issue - State: closed - Opened by tioluwani94 almost 6 years ago
Labels: BookingListPage

#6 - Endpoint to get the list of bookings. It must fufil the following conditions

Issue - State: closed - Opened by tioluwani94 almost 6 years ago
Labels: BookingListPage

#5 - Loading the booking list data on componentDidMount

Issue - State: closed - Opened by tioluwani94 almost 6 years ago
Labels: BookingListPage

#4 - Clicking on the BookingList Item should transistion to the Booking Detail Page

Issue - State: open - Opened by tioluwani94 almost 6 years ago
Labels: BookingListPage

#3 - Building the booking list section

Issue - State: closed - Opened by tioluwani94 almost 6 years ago
Labels: BookingListPage

#2 - The booking Heading section which consists of the following

Issue - State: closed - Opened by tioluwani94 almost 6 years ago - 1 comment
Labels: BookingListPage

#1 - Building the booking list item in Storybook

Issue - State: closed - Opened by tioluwani94 almost 6 years ago

Ecosyste.ms: Issues

GitHub / tioluwani94/customer-success-app issues and pull requests

#20 - Use the reducer pattern in accounting for the data context when creating a provider

#19 - Create two different networks adapter that account for the following scenarios

#18 - Using Json server, create a mock api-call to send down the list of entities (bookings, clients, tutors, etc)

#17 - The logic to implement the server side search. When no result is found, just display no result found.

#16 - The worked on bookings would be stored in the provider. The format includes just an array of the booking orders.

#15 - Design the Tutor Item Component. This consist of the name and the email.

#14 - Design the Tutor list component as well as the search. [should also account for client and server search]

#13 - Endpoint to fetch the list of tutors. using json-server and accounting for the search functionality also

#12 - Design the Client List Item Page. this consist of the name of the client, the email and the phone number of the client.

#11 - Design the Client List Page and the Search bar which accounts for both client and server search

#10 - Endpoint to implement the fetching of client data.

#9 - the logic to implement the server side filtering. This doesn't consider when there is an array of worked bookings.

#8 - The Logic to implement the Client side search. If there is no result, the default text that shows when the result is empty also suggest to check the server for the data. Clicking on the suggestion changes the checkbox state to server.

#7 - The logic to implement Client side filtering for the following

#6 - Endpoint to get the list of bookings. It must fufil the following conditions

#5 - Loading the booking list data on componentDidMount

#4 - Clicking on the BookingList Item should transistion to the Booking Detail Page

#3 - Building the booking list section

#2 - The booking Heading section which consists of the following

#1 - Building the booking list item in Storybook