js-cookie-rails 2.0.0.pre.beta.1.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (43) hide show
  1. checksums.yaml +7 -0
  2. data/Gemfile +2 -0
  3. data/LICENSE +21 -0
  4. data/README.md +35 -0
  5. data/Rakefile +71 -0
  6. data/VERSION +1 -0
  7. data/js-cookie-rails.gemspec +31 -0
  8. data/lib/js-cookie-rails.rb +1 -0
  9. data/lib/js-cookie-rails/rails.rb +1 -0
  10. data/lib/js-cookie-rails/rails/engine.rb +6 -0
  11. data/spec/dummy/README.rdoc +261 -0
  12. data/spec/dummy/Rakefile +7 -0
  13. data/spec/dummy/app/assets/javascripts/application.js +15 -0
  14. data/spec/dummy/app/assets/stylesheets/application.css +13 -0
  15. data/spec/dummy/app/controllers/application_controller.rb +3 -0
  16. data/spec/dummy/app/helpers/application_helper.rb +2 -0
  17. data/spec/dummy/app/views/layouts/application.html.erb +14 -0
  18. data/spec/dummy/config.ru +4 -0
  19. data/spec/dummy/config/application.rb +65 -0
  20. data/spec/dummy/config/boot.rb +10 -0
  21. data/spec/dummy/config/database.yml +25 -0
  22. data/spec/dummy/config/environment.rb +5 -0
  23. data/spec/dummy/config/environments/development.rb +37 -0
  24. data/spec/dummy/config/environments/production.rb +67 -0
  25. data/spec/dummy/config/environments/test.rb +37 -0
  26. data/spec/dummy/config/initializers/backtrace_silencers.rb +7 -0
  27. data/spec/dummy/config/initializers/inflections.rb +15 -0
  28. data/spec/dummy/config/initializers/mime_types.rb +5 -0
  29. data/spec/dummy/config/initializers/secret_token.rb +7 -0
  30. data/spec/dummy/config/initializers/session_store.rb +8 -0
  31. data/spec/dummy/config/initializers/wrap_parameters.rb +14 -0
  32. data/spec/dummy/config/locales/en.yml +5 -0
  33. data/spec/dummy/config/routes.rb +58 -0
  34. data/spec/dummy/db/test.sqlite3 +0 -0
  35. data/spec/dummy/public/404.html +26 -0
  36. data/spec/dummy/public/422.html +26 -0
  37. data/spec/dummy/public/500.html +25 -0
  38. data/spec/dummy/public/favicon.ico +0 -0
  39. data/spec/dummy/script/rails +6 -0
  40. data/spec/js-cookie-rails_spec.rb +12 -0
  41. data/spec/spec_helper.rb +16 -0
  42. data/vendor/assets/javascripts/js.cookie.js +137 -0
  43. metadata +202 -0
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA1:
3
+ metadata.gz: 0d93cd5cb86cf64acb4343b2df2f698ea92f437c
4
+ data.tar.gz: 252b7b1e45c4bff85d5052fc24211a7557b36078
5
+ SHA512:
6
+ metadata.gz: dd38489b5a015d55e97420467c06fbb39f577f1b6001680e39c082e2ddbb0cc994126f5b29e55f788f3b71625e52b8a9f5d70d2f2cdd46c712405c66f6961acb
7
+ data.tar.gz: 0955e0a3bccddc9c756634b31573602da7bec41f9c3ff7548557f55ff1f61a6c24c9a13812714684ed54f8d0733024f9c6a0553b6f0e0e8b42169cce9ad79122
data/Gemfile ADDED
@@ -0,0 +1,2 @@
1
+ source 'http://rubygems.org'
2
+ gemspec
data/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ The MIT License
2
+
3
+ Copyright (c) 2015 Ryan Scott Lewis <ryan@rynet.us>
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in
13
+ all copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
21
+ THE SOFTWARE.
@@ -0,0 +1,35 @@
1
+ # js-cookie-rails
2
+
3
+ Adds [js-cookie](https://github.com/js-cookie/js-cookie) to the Rails 3 asset pipeline.
4
+
5
+ ## Installation
6
+
7
+ In your Gemfile, add the following line:
8
+
9
+ ```ruby
10
+ gem 'js-cookie-rails'
11
+ ```
12
+
13
+ Now run `bundle install`.
14
+
15
+ ### Rails 3.2 or greater
16
+
17
+ For Rails 3.2 and greater, the files will be added to the asset pipeline and available for you to use.
18
+
19
+ Simply the following to `app/assets/javascripts/application.js`:
20
+
21
+ //= require js.cookie
22
+
23
+ ## Contributing
24
+
25
+ * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
26
+ * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
27
+ * Fork the project
28
+ * Start a feature/bugfix branch
29
+ * Commit and push until you are happy with your contribution
30
+ * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
31
+ * Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
32
+
33
+ ## Copyright
34
+
35
+ Copyright © 2015 Ryan Scott Lewis. See LICENSE for details.
@@ -0,0 +1,71 @@
1
+ require 'rubygems/package_task'
2
+ require 'logger'
3
+ require 'pathname'
4
+
5
+ $logger = Logger.new(STDOUT)
6
+ $project_path = Pathname.new(__FILE__).dirname.expand_path
7
+ $spec = eval( $project_path.join('js-cookie-rails.gemspec').read )
8
+
9
+ Rake::TaskManager.record_task_metadata = true
10
+
11
+ def run_command(command)
12
+ result = `#{command}`.chomp.strip
13
+ message = command
14
+
15
+ message << "\n" + result.lines.collect { |line| " #{line}" }.join unless result.empty?
16
+
17
+ $logger.debug(message)
18
+
19
+ result
20
+ end
21
+
22
+ Gem::PackageTask.new($spec) do |task|
23
+ task.need_zip = false
24
+ end
25
+
26
+ namespace :js_cookie do
27
+ desc 'Update the `js-cookie` submodule'
28
+ task :update do
29
+ js_cookie_path = $project_path.join('lib', 'js-cookie')
30
+
31
+ run_command("cd #{js_cookie_path} && git pull origin master")
32
+ js_cookie_latest_tag = run_command("cd #{js_cookie_path} && git describe --abbrev=0 --tags")
33
+ run_command "cd #{js_cookie_path} && git checkout #{js_cookie_latest_tag}"
34
+ end
35
+
36
+ desc 'Copy the `js.cookie.js` file to the `vendor/assets/javascripts` folder'
37
+ task :vendor do
38
+ js_cookie_script_path = $project_path.join('lib', 'js-cookie', 'src', 'js.cookie.js')
39
+ vendor_path = $project_path.join('vendor', 'assets', 'javascripts')
40
+ vendor_path.mkpath
41
+
42
+ run_command "cp #{js_cookie_script_path} #{vendor_path}"
43
+ end
44
+ end
45
+
46
+ desc 'Update js-cookie and copy `js.cookie.js` into vendor'
47
+ task :js_cookie => ['js_cookie:update', 'js_cookie:vendor']
48
+
49
+ desc 'Update js-cookie, update js-cookie-rails version, tag on git'
50
+ task :update => :js_cookie do
51
+ js_cookie_path = $project_path.join('lib', 'js-cookie')
52
+ js_cookie_latest_tag = run_command("cd #{js_cookie_path} && git describe --abbrev=0 --tags")
53
+ js_cookie_version = js_cookie_latest_tag.gsub(/^v/, '')
54
+
55
+ # Save new gem version
56
+ gem_version_path = $project_path.join('VERSION')
57
+ gem_version = "#{js_cookie_version}.0"
58
+
59
+ File.open(gem_version_path, 'w') {|f| f.write(gem_version) }
60
+
61
+ # Commit
62
+ run_command "git add ."
63
+ run_command "git commit -m \"Version bump to #{gem_version} (js-rails version #{js_cookie_version})\""
64
+ run_command "git tag #{gem_version}"
65
+ end
66
+
67
+ task :default do
68
+ Rake::application.options.show_tasks = :tasks # this solves sidewaysmilk problem
69
+ Rake::application.options.show_task_pattern = //
70
+ Rake::application.display_tasks_and_comments
71
+ end
data/VERSION ADDED
@@ -0,0 +1 @@
1
+ 2.0.0-beta.1.0
@@ -0,0 +1,31 @@
1
+ # -*- encoding: utf-8 -*-
2
+ Gem::Specification.new do |s|
3
+
4
+ # Variables
5
+ s.name = 'js-cookie-rails'
6
+ s.author = 'Ryan Scott Lewis'
7
+ s.email = 'ryan@rynet.us'
8
+ s.summary = 'Use js-cookie with Rails 3'
9
+ s.description = 'This gem provides js-cookie assets for your Rails 3 application.'
10
+ s.license = 'MIT'
11
+
12
+ # Dependencies
13
+ s.add_dependency 'railties', '>= 3.2.0', '< 5.0'
14
+ s.add_development_dependency 'rails', '~> 3.2'
15
+ s.add_development_dependency 'sqlite3', '~> 1.3'
16
+ s.add_development_dependency 'uglifier', '~> 1.3'
17
+ s.add_development_dependency 'sass', '~> 3.2'
18
+ s.add_development_dependency 'rake', '~> 10.0'
19
+ s.add_development_dependency 'rspec-rails', '~> 2.13'
20
+ s.add_development_dependency 'fuubar', '~> 1.1'
21
+ s.required_rubygems_version = ">= 1.3.6"
22
+
23
+ # Pragmatically set variables
24
+ s.homepage = "http://github.com/RyanScottLewis/#{s.name}"
25
+ s.version = Pathname.glob('VERSION*').first.read rescue '0.0.0'
26
+ s.require_paths = ['lib']
27
+ s.files = %w(Gemfile js-cookie-rails.gemspec LICENSE Rakefile README.md VERSION vendor/assets/javascripts/js.cookie.js)
28
+ s.files += Dir.glob('lib/*.rb')
29
+ s.files += Dir.glob('lib/js-cookie-rails/**/*.rb')
30
+ s.files += Dir.glob('spec/**/*')
31
+ end
@@ -0,0 +1 @@
1
+ require 'js-cookie-rails/rails'
@@ -0,0 +1 @@
1
+ require 'js-cookie-rails/rails/engine'
@@ -0,0 +1,6 @@
1
+ module JsCookie
2
+ module Rails
3
+ class Engine < ::Rails::Engine
4
+ end
5
+ end
6
+ end
@@ -0,0 +1,261 @@
1
+ == Welcome to Rails
2
+
3
+ Rails is a web-application framework that includes everything needed to create
4
+ database-backed web applications according to the Model-View-Control pattern.
5
+
6
+ This pattern splits the view (also called the presentation) into "dumb"
7
+ templates that are primarily responsible for inserting pre-built data in between
8
+ HTML tags. The model contains the "smart" domain objects (such as Account,
9
+ Product, Person, Post) that holds all the business logic and knows how to
10
+ persist themselves to a database. The controller handles the incoming requests
11
+ (such as Save New Account, Update Product, Show Post) by manipulating the model
12
+ and directing data to the view.
13
+
14
+ In Rails, the model is handled by what's called an object-relational mapping
15
+ layer entitled Active Record. This layer allows you to present the data from
16
+ database rows as objects and embellish these data objects with business logic
17
+ methods. You can read more about Active Record in
18
+ link:files/vendor/rails/activerecord/README.html.
19
+
20
+ The controller and view are handled by the Action Pack, which handles both
21
+ layers by its two parts: Action View and Action Controller. These two layers
22
+ are bundled in a single package due to their heavy interdependence. This is
23
+ unlike the relationship between the Active Record and Action Pack that is much
24
+ more separate. Each of these packages can be used independently outside of
25
+ Rails. You can read more about Action Pack in
26
+ link:files/vendor/rails/actionpack/README.html.
27
+
28
+
29
+ == Getting Started
30
+
31
+ 1. At the command prompt, create a new Rails application:
32
+ <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
33
+
34
+ 2. Change directory to <tt>myapp</tt> and start the web server:
35
+ <tt>cd myapp; rails server</tt> (run with --help for options)
36
+
37
+ 3. Go to http://localhost:3000/ and you'll see:
38
+ "Welcome aboard: You're riding Ruby on Rails!"
39
+
40
+ 4. Follow the guidelines to start developing your application. You can find
41
+ the following resources handy:
42
+
43
+ * The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
44
+ * Ruby on Rails Tutorial Book: http://www.railstutorial.org/
45
+
46
+
47
+ == Debugging Rails
48
+
49
+ Sometimes your application goes wrong. Fortunately there are a lot of tools that
50
+ will help you debug it and get it back on the rails.
51
+
52
+ First area to check is the application log files. Have "tail -f" commands
53
+ running on the server.log and development.log. Rails will automatically display
54
+ debugging and runtime information to these files. Debugging info will also be
55
+ shown in the browser on requests from 127.0.0.1.
56
+
57
+ You can also log your own messages directly into the log file from your code
58
+ using the Ruby logger class from inside your controllers. Example:
59
+
60
+ class WeblogController < ActionController::Base
61
+ def destroy
62
+ @weblog = Weblog.find(params[:id])
63
+ @weblog.destroy
64
+ logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
65
+ end
66
+ end
67
+
68
+ The result will be a message in your log file along the lines of:
69
+
70
+ Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
71
+
72
+ More information on how to use the logger is at http://www.ruby-doc.org/core/
73
+
74
+ Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
75
+ several books available online as well:
76
+
77
+ * Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
78
+ * Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
79
+
80
+ These two books will bring you up to speed on the Ruby language and also on
81
+ programming in general.
82
+
83
+
84
+ == Debugger
85
+
86
+ Debugger support is available through the debugger command when you start your
87
+ Mongrel or WEBrick server with --debugger. This means that you can break out of
88
+ execution at any point in the code, investigate and change the model, and then,
89
+ resume execution! You need to install ruby-debug to run the server in debugging
90
+ mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
91
+
92
+ class WeblogController < ActionController::Base
93
+ def index
94
+ @posts = Post.all
95
+ debugger
96
+ end
97
+ end
98
+
99
+ So the controller will accept the action, run the first line, then present you
100
+ with a IRB prompt in the server window. Here you can do things like:
101
+
102
+ >> @posts.inspect
103
+ => "[#<Post:0x14a6be8
104
+ @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
105
+ #<Post:0x14a6620
106
+ @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
107
+ >> @posts.first.title = "hello from a debugger"
108
+ => "hello from a debugger"
109
+
110
+ ...and even better, you can examine how your runtime objects actually work:
111
+
112
+ >> f = @posts.first
113
+ => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
114
+ >> f.
115
+ Display all 152 possibilities? (y or n)
116
+
117
+ Finally, when you're ready to resume execution, you can enter "cont".
118
+
119
+
120
+ == Console
121
+
122
+ The console is a Ruby shell, which allows you to interact with your
123
+ application's domain model. Here you'll have all parts of the application
124
+ configured, just like it is when the application is running. You can inspect
125
+ domain models, change values, and save to the database. Starting the script
126
+ without arguments will launch it in the development environment.
127
+
128
+ To start the console, run <tt>rails console</tt> from the application
129
+ directory.
130
+
131
+ Options:
132
+
133
+ * Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
134
+ made to the database.
135
+ * Passing an environment name as an argument will load the corresponding
136
+ environment. Example: <tt>rails console production</tt>.
137
+
138
+ To reload your controllers and models after launching the console run
139
+ <tt>reload!</tt>
140
+
141
+ More information about irb can be found at:
142
+ link:http://www.rubycentral.org/pickaxe/irb.html
143
+
144
+
145
+ == dbconsole
146
+
147
+ You can go to the command line of your database directly through <tt>rails
148
+ dbconsole</tt>. You would be connected to the database with the credentials
149
+ defined in database.yml. Starting the script without arguments will connect you
150
+ to the development database. Passing an argument will connect you to a different
151
+ database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
152
+ PostgreSQL and SQLite 3.
153
+
154
+ == Description of Contents
155
+
156
+ The default directory structure of a generated Ruby on Rails application:
157
+
158
+ |-- app
159
+ | |-- assets
160
+ | |-- images
161
+ | |-- javascripts
162
+ | `-- stylesheets
163
+ | |-- controllers
164
+ | |-- helpers
165
+ | |-- mailers
166
+ | |-- models
167
+ | `-- views
168
+ | `-- layouts
169
+ |-- config
170
+ | |-- environments
171
+ | |-- initializers
172
+ | `-- locales
173
+ |-- db
174
+ |-- doc
175
+ |-- lib
176
+ | `-- tasks
177
+ |-- log
178
+ |-- public
179
+ |-- script
180
+ |-- test
181
+ | |-- fixtures
182
+ | |-- functional
183
+ | |-- integration
184
+ | |-- performance
185
+ | `-- unit
186
+ |-- tmp
187
+ | |-- cache
188
+ | |-- pids
189
+ | |-- sessions
190
+ | `-- sockets
191
+ `-- vendor
192
+ |-- assets
193
+ `-- stylesheets
194
+ `-- plugins
195
+
196
+ app
197
+ Holds all the code that's specific to this particular application.
198
+
199
+ app/assets
200
+ Contains subdirectories for images, stylesheets, and JavaScript files.
201
+
202
+ app/controllers
203
+ Holds controllers that should be named like weblogs_controller.rb for
204
+ automated URL mapping. All controllers should descend from
205
+ ApplicationController which itself descends from ActionController::Base.
206
+
207
+ app/models
208
+ Holds models that should be named like post.rb. Models descend from
209
+ ActiveRecord::Base by default.
210
+
211
+ app/views
212
+ Holds the template files for the view that should be named like
213
+ weblogs/index.html.erb for the WeblogsController#index action. All views use
214
+ eRuby syntax by default.
215
+
216
+ app/views/layouts
217
+ Holds the template files for layouts to be used with views. This models the
218
+ common header/footer method of wrapping views. In your views, define a layout
219
+ using the <tt>layout :default</tt> and create a file named default.html.erb.
220
+ Inside default.html.erb, call <% yield %> to render the view using this
221
+ layout.
222
+
223
+ app/helpers
224
+ Holds view helpers that should be named like weblogs_helper.rb. These are
225
+ generated for you automatically when using generators for controllers.
226
+ Helpers can be used to wrap functionality for your views into methods.
227
+
228
+ config
229
+ Configuration files for the Rails environment, the routing map, the database,
230
+ and other dependencies.
231
+
232
+ db
233
+ Contains the database schema in schema.rb. db/migrate contains all the
234
+ sequence of Migrations for your schema.
235
+
236
+ doc
237
+ This directory is where your application documentation will be stored when
238
+ generated using <tt>rake doc:app</tt>
239
+
240
+ lib
241
+ Application specific libraries. Basically, any kind of custom code that
242
+ doesn't belong under controllers, models, or helpers. This directory is in
243
+ the load path.
244
+
245
+ public
246
+ The directory available for the web server. Also contains the dispatchers and the
247
+ default HTML files. This should be set as the DOCUMENT_ROOT of your web
248
+ server.
249
+
250
+ script
251
+ Helper scripts for automation and generation.
252
+
253
+ test
254
+ Unit and functional tests along with fixtures. When using the rails generate
255
+ command, template test files will be generated for you and placed in this
256
+ directory.
257
+
258
+ vendor
259
+ External libraries that the application depends on. Also includes the plugins
260
+ subdirectory. If the app has frozen rails, those gems also go here, under
261
+ vendor/rails/. This directory is in the load path.