Rails 5敏捷web开发经典指南：实战与推荐

4星 · 超过85%的资源需积分: 31 196 浏览量更新于2024-07-18 1 收藏 15.72MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

learning curve. So while we’re still watching this, for the moment it remains

an advanced topic beyond the scope of this book. We’re confident that

those who find themselves needing this feature can find the material they

need online. More on this point later.

Turbolinks 3

Turbolinks 3, although technically a separate package, is something that

Rails applications depend on by default, so it might as well be considered

part of the core. So why isn’t it covered more?

Mostly because it’s too successful at being transparent. When it works,

you don’t have to think about it. It just makes things faster.

Prior editions of this book covered disabling Turbolinks when it got in the

way. This turns out not to be necessary for the scenarios in this book, so

Turbolinks has less coverage in this edition than in prior editions.

So what changes got comparatively more coverage?

• By far the change with the biggest impact is that all of the

rake

tasks have

been replaced by the

rails

command. For example,

rake test

has become

rails

test

. For the most part, this was a global search and replace. But what’s

notable is that it isn’t explicitly covered, because the target audience for

the book is people new to Rails, and spending a lot of time covering the

way things used to be isn’t helpful to them.

• Controller tests now are integration tests instead of essentially unit tests.

This also means that methods such as

assigns()

have been moved out of

Rails (but can still be added via the

rails-controller-testing

gem). Most definitely

not a simple search and replace, this change required many tests to be

completely rewritten. But again, the changes aren’t highlighted—the focus

of the book is on what works now.

• Synchronous mail delivery has been replaced by asynchronous mail

delivery. This is largely transparent to the application but required some

changes to the tests.

There were other changes. For example,

belongs_to

is now required by default.

This required one existing relationship to be changed to be explicitly marked

as optional. But the preceding features affected more pages.

So what does this mean to you, the reader?

It’s important to understand this book in the context of the web as it exists

today. The first edition of this book predated Stack Overflow, Hacker News,

GitHub, and many other resources that are available now. These days, if you

report erratum • discuss

Preface to the Rails 5 Edition • xv

Rails applications are written in Ruby, a modern, object-oriented scripting

language. Ruby is concise without being unintelligibly terse. You can express

ideas naturally and cleanly in Ruby code. This leads to programs that are

easy to write and (just as important) are easy to read months later.

Rails takes Ruby to the limit, extending it in novel ways that make a program-

mer’s life easier. This makes our programs shorter and more readable. It also

allows us to perform tasks that would normally be done in external configu-

ration files inside the codebase instead. This makes it far easier to see what’s

happening. The following code defines the model class for a project. Don’t

worry about the details for now. Instead, think about how much information

is being expressed in a few lines of code:

class Project < ApplicationRecord

belongs_to :portfolio

has_one :project_manager

has_many :milestones

has_many :deliverables, through: milestones

validates :name, :description, presence: true

validates :non_disclosure_agreement, acceptance: true

validates :short_name, uniqueness: true

end

Two other philosophical underpinnings keep Rails code short and readable:

DRY and convention over configuration. DRY stands for don’t repeat yourself.

Every piece of knowledge in a system should be expressed in one place. Rails

uses the power of Ruby to bring that to life. You’ll find little duplication in a

Rails application; you say what you need to say in one place—a place often

suggested by the conventions of the MVC architecture—and then move on.

For programmers used to other web frameworks, where a simple change to

the schema could involve a dozen or more code changes, this was a revelation.

Convention over configuration is crucial, too. It means that Rails has sensible

defaults for just about every aspect of knitting together your application.

Follow the conventions, and you can write a Rails application using less code

than a typical Java web application uses in XML configuration. If you need

to override the conventions, Rails makes that easy, too.

Developers coming to Rails found something else, too. Rails doesn’t merely

play catch-up with the de facto web standards; it helps define them. And

Rails makes it easy for developers to integrate features such as Ajax, RESTful

interfaces, and WebSockets into their code because support is built in. (And

if you’re not familiar with Ajax, REST interfaces, or WebSockets, never fear—

we’ll explain what these terms mean in Chapter 11, Task F: Add a Dash of

Ajax, on page 145 and REST: Representational State Transfer, on page 316.)

Introduction • xx

report erratum • discuss

剩余466页未读，继续阅读

yinkaisheng-nj

粉丝: 762
资源: 6231

Rails 5敏捷web开发经典指南：实战与推荐

The Rails 5 Way(4th) 无水印原版pdf

rails敏捷开发最新第三版（中英文）Part1

敏捷开发知识体系--高清版.pdf

What are the most significant differences among structured, object-oriented, and agile methods? What do they have in common?

Test-Driven Development

历年北京联合大学软件工程英语口语复试题目

学习后端应该准备什么书籍

agile 和scrum的关系

agile_modbusrtu

iterative model

agile modbus教程

python系统需求规格说明书参考文献

qca芯片Agile模式开启不了

推荐的代码规范学习资料

agile 9.3.1.2

Agile Controller-Campus 下载

agile java

安装Agile controller

agile controller

最新资源