I'm about 9 days in to the development of the application. The tutorial videos were completed a few days ago and were about 6 hours in length. the tutorials mainly helped to set up the Controllers, Models, and Services. There was a basic tutorial on Views, but there was much missing in terms of actually getting the application functional. However, this is obviously a good opportunity to learn!
I spent a couple of evenings sorting the appearance out, and carving in a rather nice bootstrap template I found.
Today I got the functionality of the movie import search bar to work. The search bar uses Bloodhound's typeahead feature to search and provide results from the TMDB API. More on this to come in a future post when I properly dissect the example code.
I also implement a new Controller method which similarly to the above, allows the user to search TMDB for a movie, and then displays the results in an view. This does not use Bloodhound's typeahead feature.
I was happy with the improvement in my debugging skills as I could not initially get a successful http response from TMDB API when using the search term, even though the application did this successfully in a similar manner when searching for the homepage categories (e.g. top rated movies).
I used the VS debugger to copy the requestUri prior to the failed response, then copied to notepad for reference, to compare to the structure of the requestUri from the successful category search responses. I also pasted the bad requestUri into google to see what would happen...
Funnily enough the request in a browser must have been redirected to the correct address path, because then I could see (in browser) the JSON file I was expecting. After pasting this back in to notepad to inspect the differences, I noticed a forward slash / in front of the ?api_key text. I then used the following code to amend the requestUri:
- requestUri = requestUri.Replace("/movie/", "/movie");
By breaking down the steps, I was able to try and make sense of something that initially seemed incomprehensible, and more importantly - I got it to work.
Next steps are to continue implementing more views and functionality.