Read (or re-read) the following chapters from our book(it’s in our library):
We're no longer using the
Asnaming convention when extending mo...
curlto save a copy of
curlto save the CSS stylesheet of sueddeutsche.de
SSL / TLS
Read about the following software engineering principles:
Look at the repo for your MovieDB, look at the repo for Cards. Find some examples where the principle was used, find some examples where it was violated.
While working on a Rails application, your code base will grow a collection of different file types including:
Except for the Ruby part, all these files are shipped to the browser. In this card we'll focus specifically on CSS, JS, fonts and static media files which are often summed up as assets.
You might already have noticed that Rails modifies those assets before delivering ...
/assets folder are processed and delivered to the browser. Rails has a second pipeline called webpacker, which we will cover later.
We are we using the BEM pattern ("Block, Element, Modifier") to structure our CSS in all new projects. We try to migrate legacy projects to BEM, block-by-block.
Read the chapter "Taming Stylesheets" from our book(in our library).
Talk with a colleague about the reasons for the naming conventions we use:
.block .block--element .block.-modifier
Why are elements preceded by a...
While we don't use CoffeeScript in new projects any more, we require you to understand it enough to work on existing projects that use it.
Take a look at the popularlibrary.
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?
Understand this article: [Rails 5, Module#prepend, and the End of
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 --> rejected rejected --> pending pending --> accepted
Change the visibility rules (Consul powers) so:
On the Movie DB index, show a random actor who was born today:
Automatically retrieve the year of a movie for any new movie entered into MovieDB, using the. For the UI this means that there is no longer a "Year" ...
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...