Sha256: 7cde65c3e902df276d603ba1ab746b4ef2a515d45a89ffbaa38360aa181ae001
Contents?: true
Size: 1.54 KB
Versions: 55
Compression:
Stored size: 1.54 KB
Contents
module SuperScaffoldBase
extend ActiveSupport::Concern
included do
# ##############################
#
# TODO: Should we retain some of these class options?
#
# By default we inherit a bunch of options that _would_ automatically be used if we
# were writing a normal Rails generator that used normal methods of generating files.
# So if you invoke this generator without passing any arguments (and without these
# remove_class_option lines) then at the top of the help text you'd see info about all
# of these options:
#
# ##############################
#
# rails g super_scaffold
#
# Options:
# [--skip-namespace], [--no-skip-namespace] # Skip namespace (affects only isolated engines)
# [--skip-collision-check], [--no-skip-collision-check] # Skip collision check
#
# Runtime options:
# -f, [--force] # Overwrite files that already exist
# -p, [--pretend], [--no-pretend] # Run but do not make any changes
# -q, [--quiet], [--no-quiet] # Suppress status output
# -s, [--skip], [--no-skip] # Skip files that already exist
#
# ##############################
#
# Maye we have comparable options for some of these and should retain them and
# pass them through to the rake task?
remove_class_option :skip_namespace
remove_class_option :skip_collision_check
remove_class_option :force
remove_class_option :pretend
remove_class_option :quiet
remove_class_option :skip
end
end
Version data entries
55 entries across 55 versions & 1 rubygems