Read (or re-read) the following chapters from our book Growing Rails Applications in Practice Archive (it’s in our library):
Note
We're no longer using the
Asnaming convention when extending mo...
curl to save a copy of http://www.sueddeutsche.de/.curl to save the CSS stylesheet of sueddeutsche.deSSL / 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 ...
The asset pipeline is one of Rails' two mechanisms how stylesheets, javascripts and images from your /assets folder are processed and delivered to the browser. Rails has a second pipeline called webpacker, which we will cover later.
Congratulations, you just made it through about half of our curriculum deck! 🎉
We've covered the basics of your future stack and are about to dive deeper in some more advanced topics.
Now, read the article " Parting advice from an older Software Engineer Archive ". Try to memorize the key takeaways of 1-5 on the list.
Before you move on, add two reminders to your calendar:
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 Growing Rails Applications in Practice Archive (in our library).
Talk with a colleague about the reasons for the naming conventions ...
Stepping forward from JavaScript Basics, the goal of this card is for you to be able to read and write more complex ES6+ code.
Read The JavaScript Object Model: A deep dive into prototypes and properties.
There's also a video Archive of that talk in our internal library.
Understand how asynchronous JavaScript works:
Just like we use gems on the server, we use third party JavaScript libraries in the browser. These typically provide functionality like:
We generally use the yarn add command to add third party libraries to our application. It will persist the desired library version within the "package.json" file and pin matching d...
In a web application you often need to move data between the client (HTML, Javascript) and the server (Ruby, Rails).
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 [input](https://makandracards.com/makandra/33699-input-a-dom-event-that-is-fired-whenever-a-text-field-cha...
Read the following Rubymonk articles:
Understand all the terms in How Ruby method lookup works, in particular:
includeextendprependDo you understand why object.extend(SomeModule) is the same as object.singleton_class.include(SomeModule)?
How does include and 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:
draftpendingacceptedrejectedA 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: Reason
rejected --> pending
pending --> accepted
Change the visibility rules (Consul powers) so:
On the start page of your Movie DB, show a random actor who was born today:
Tip
Consider the best place to put the new logic. Should it be an existing class or a new class?
Automatically retrieve the year of a movie for any new movie entered into MovieDB, using the [themov...