Skip to content

Commit a8dd1cd

Browse files
committed
Publish article 'Working with images in Nuxt Content'
1 parent d7ef42b commit a8dd1cd

6 files changed

+523
-278
lines changed
Loading

content/articles/creating-a-full-stack-kanban-board-the-ruby-on-rails-api-backend.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ For our last step, we’ll also uncomment the rack-cors gem in the Gemfile, we
116116

117117
```ruby
118118
...
119-
\# Use Rack CORS for handling Cross-Origin Resource Sharing (CORS), making cross-origin AJAX possible
119+
# Use Rack CORS for handling Cross-Origin Resource Sharing (CORS), making cross-origin AJAX possible
120120
gem 'rack-cors'
121121
...
122122
```
@@ -129,13 +129,13 @@ Now our project and database should be setup! To test if everything is working c
129129

130130
Since the cards belong to a user and column, we’ll first set up these endpoints. We also don’t need to support all CRUD operations for the columns and users, so this will only require an index route.
131131

132-
So let’s create the necessary model & controller.
132+
Let’s start by creating the necessary model & controller.
133133

134134
### 2.1 Create the column model
135135

136136
To generate the model, run: ```rails g model column label value```
137137

138-
Both the label and value will be strings, this is the default value for the model generator so we don’t need to specify the data type for these columns. If we’d want a column to have another value then we’d need to define it as for example ```rails g model column label:text value:integer```
138+
Both the label and value columns will be strings, this is the default value for the model generator so we don’t need to specify the data type for these columns. If we’d want a column to have another value then we’d need to define it as for example ```rails g model column label:text value:integer```
139139

140140
Once the generator is finished, run the migration: ```rails db:migrate```
141141

0 commit comments

Comments
 (0)