Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Building Extensions - best practises
Search
Peter Berkenbosch
February 27, 2014
0
57
Building Extensions - best practises
SpreeConf 2014 Lightning talk.
Peter Berkenbosch
February 27, 2014
Tweet
Share
More Decks by Peter Berkenbosch
See All by Peter Berkenbosch
Open source contribution with Spree
pberkenbosch
1
200
Spree Commerce hub for developers
pberkenbosch
0
180
Behavior Driven Development, an introduction
pberkenbosch
1
52
TDD Spree
pberkenbosch
5
460
Twente RB Spree from the trenches
pberkenbosch
0
52
GroningenRB Spree from the trenches
pberkenbosch
0
110
Spree from the Trenches
pberkenbosch
3
330
[dutch] Behavior Driven Development
pberkenbosch
1
70
BDD Outside in development
pberkenbosch
1
160
Featured
See All Featured
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
31
9.7k
Designing Experiences People Love
moore
142
24k
Leading Effective Engineering Teams in the AI Era
addyosmani
3
360
Bash Introduction
62gerente
615
210k
We Have a Design System, Now What?
morganepeng
53
7.8k
Building a Modern Day E-commerce SEO Strategy
aleyda
43
7.7k
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
15
1.7k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
35
3.2k
A better future with KSS
kneath
239
18k
Agile that works and the tools we love
rasmusluckow
331
21k
Six Lessons from altMBA
skipperchong
28
4k
Music & Morning Musume
bryan
46
6.8k
Transcript
Building Extensions best practises ! Peter Berkenbosch
Unix philosophy building short, simple, clear, modular, and extendable code
that can be easily maintained and repurposed by developers other than its creators.
Documentation
Modular
OOP
Extension as “Model”
Models Views Controllers Assets Overrides Rails::Engine Spree other 3rd party
gems extension
Looks familier! Rails anyone?!
Outside In
Models Views Controllers Assets Overrides Rails::Engine Spree other 3rd party
gems extension
Test the “interface” can be just an API
Drives Quality
Self documenting
gem install spree_cmd
spree extension
git clone spree
rake sandbox
spree extension
module SpreeSales! class Engine < Rails::Engine! require 'spree/core'! isolate_namespace Spree!
engine_name 'spree_sales'! ! # use rspec for tests! config.generators do |g|! g.test_framework :rspec! end! ! def self.activate! Dir.glob(File.join(File.dirname(__FILE__), '../../app/**/*_decorator*.rb')) do |c|! Rails.configuration.cache_classes ? require(c) : load(c)! end! end! ! config.to_prepare &method(:activate).to_proc! end! end
Spree Testing Support
Usual suspect rspec capybara factory_girl
# Requires factories defined in spree_core! require 'spree/testing_support/factories'! require 'spree/testing_support/controller_requests'!
require 'spree/testing_support/authorization_helpers'! require 'spree/testing_support/url_helpers'
Red - Green - Refacor Repeat
Nothing new. TDD / BDD …
Extending Spree
class_evil Looking at adding durable_decorator
Deface for small changes
override view file for the more complex customisations
Deface-able views ! for easy overriding the overrides.
github.com/spree/spree_ Inspiration and collaboration!