Add a find-as-you-type search to MovieDB. Above the list of movies there should be a text input that updates the list with the search results as the user is typing in the query. The user should not have to press a "Search" button (hint: you can bind to the [
Understand all the terms in How Ruby method lookup works, in particular:
Do you understand why
object.extend(SomeModule) is the same as
extend work together with inheritance?
You may also read more about the Ruby Object Model, if all o...
Movies in MovieDB should have one of the following workflow states:
A movie always begins as a
draft and then transitions through the states as it's getting reviewed. This could be a typical state flow for a movie:
stateDiagram-v2 [*] --> draft draft --> pending pending --> declined: Reason declined --> pending pending --> published
Change the visibility rules (Consul powers) so:
On the start page of your Movie DB, show the title of a random movie that is coming soon to theaters.
Consider the best place to put the new logic. Should it be an existing class or a new class?
Jasmine is a purely client-side tool. It cannot ask Rails to render a view or access the database. Any HTTP calls must be mocked.
For example, when you want to test that a date picker opens a calenda...
Add the following feature to MovieDB:
Read the following material:
If you've stumbled over
display: grid while reading the Flexbox material of the previous card - we've got you covered!
Let's dive into this topic with a quote:
Flexbox is made for one-dimensional layouts and Grid is made for two-dimensional layouts.
You will learn more subtle differences in the linked material below, but you can remember this as a rule of thumb.
Many of our clients can't or don't want to design their user interfaces. In the absence of a good UI design, you should always be able to come up with a default. Since the user interface makes up 70% of a typical web application, this is closely related to requirements analysis and cost estimation.
Talk with your mentor about the following topics:
Read the following chapters from our book Growing Rails Applications in Practice:
Discuss each chapter with your mentor.
Work through the follow resources:
Talk to your mentor about how we're approaching applications that are either old or abandoned by a different team earlier:
bundle && rake db:create db:migrate).
Goal of this lesson is to understand what middlewares in Rack are good for.
Start with these articles:
You should be able to answer the following questions:
Some tasks in a web application are better not done live when a user request a page, but in the background. Examples are
Our two main mechanisms for background processing are
Web technology is a broad field and you cannot be an expert in all aspects.
However, it is useful to have a rough understanding of common terms and buzzwords, so that you don't seem uninformed when talking to a client or other developers.
Search the Internet for each of the following terms. Only take a couple of minutes for each and don't get into too much detail. Do get a rough idea about the advantages they promise.
rake -Twithin a Rails project)
rake statstask in the Rails gems
For each movie in MovieDB, we want to track which other movie it was inspired by. For example:
Start by adding a field
Movie#inspiration_id. In the movie form, I should be able to select the inspiring movie.
The list should:
Rails ships with two separate build pipelines: Sprockets ("asset pipeline") and Webpacker.
Read the first couple of sections of its official documentation.
You should learn how to:
Talk with a colleague and find out why we're using building some of our sites using static site generators instead of Rails.
You should talk about:
Read through the Middleman docs:
.png) and vector images (like
Browse the i...