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
56
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
Documentation Writing (for coders)
carmenintech
74
5k
The World Runs on Bad Software
bkeepers
PRO
70
11k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
162
15k
Code Reviewing Like a Champion
maltzj
525
40k
Learning to Love Humans: Emotional Interface Design
aarron
273
40k
Rails Girls Zürich Keynote
gr2m
95
14k
Side Projects
sachag
455
43k
Building a Scalable Design System with Sketch
lauravandoore
462
33k
Writing Fast Ruby
sferik
628
62k
Java REST API Framework Comparison - PWX 2021
mraible
33
8.8k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
13k
Building Adaptive Systems
keathley
43
2.7k
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!