Keep track of individual conversations in one place! The Support tool will be your helpdesk for answering all your users’ questions. Analyze user base : Sort and filter using attributes such as Plan Type or Total Spend to understand and segment your users.Find specific users : Directly search for users and view related information, instead of navigating through multiple pages of user analytics.Monitor user trends: See c harts that track user growth and detail on daily active users and total users.With this new feature, you’ll be able to… The Users section will give you insight into your users and provide controls for managing them. No more estimating analytics or guessing who your power users are. Below are some highlights of what you can look forward to. Ultimately, these conversations translated into a new API provider dashboard with extensive user management, support, and analytics features. Let’s just say, there were a lot of meeting notes! During these conversations, we’ve heard useful insights from technical recommendations to big picture strategic ideas. We’ve spent the past three months talking to providers of our 8,000 APIs. It’s also a place for API providers to manage, distribute and monetize them.
Plus the gem file needs a double check to delete unnecessary dependencies.RapidAPI isn’t just a hub of 400,000 developers to find, test and connect to APIs. I think that the Scheduler Class needs more refactoring in order to make it more efficient and delete some duplication. After that I used Postman to verify the calls responses. I TDD the development of the structure of the API - Data Base and routes. Plus I tried to comply with the MVC design pattern as much as possible. But instead I used this challenge to grasp my Rails skills. I thought in developing this API with Sinatra beacuse is simple and fast. A method that modifies the price related to season specifications.
If there are 15 minutes before a timeslot begins, and the booking's frequency meter is normal, create a last minute promotion. A method that calculates how frequently bookings are happening and compares that with that days availability, in order to modify the price if there is an evident peak on demand. SQLite was good in order to built this small MVP. At least this is an easy feature to implement, but there are other cases that are possible to happened that will require adding more complexity to the Scheduler Class.Ī different Data Base engine will be needed in order to scale. I think that converting that field data type into a string and coleccting that information as an array and storing its string representation in the data base can be a way to scale.Īdding validations and a more rubust availability controller - Scheduler Class - is necesary in order to prevent booking when there is no more availability. This method works well when there is only one overlap because its data type is Integer. When assigning boats to scpecific slots I added a field to the timeslots table that is filled by an overlap finder method. What complications can you foresee while doing this exercise? I think that the capacity at the test stage is 12 and not 8 as suggested. #POST /api/assignments - assign boat to timeslot
I didn't test more cases but I would love to do so to discuss in a meeting. Test Unit is testing routes (controllers). I decided to use Rspec and Test Unit for the sake of practice. This API was designed and developed to accomplish passport coding challenge.īuilt using Ruby on Rails-API with SQLite.