react-rails 0.8.0.0 → 0.9.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +8 -8
- data/README.md +2 -2
- data/lib/react/rails/version.rb +1 -1
- metadata +4 -4
checksums.yaml
CHANGED
@@ -1,15 +1,15 @@
|
|
1
1
|
---
|
2
2
|
!binary "U0hBMQ==":
|
3
3
|
metadata.gz: !binary |-
|
4
|
-
|
4
|
+
OWZjMTI2MDFiOTdlMTAwYjhhYmM1YzIzZDUyZGUwMjE2OTU5ZTljYg==
|
5
5
|
data.tar.gz: !binary |-
|
6
|
-
|
6
|
+
NWRlNzJhYjQ0MzZhNWE4MWQ2MjJhNWFmZGFmZDI0MWE3YWJhM2MxYw==
|
7
7
|
SHA512:
|
8
8
|
metadata.gz: !binary |-
|
9
|
-
|
10
|
-
|
11
|
-
|
9
|
+
NDVlMTZiMDFlY2JhNTE1ZjIwNjcwMzQwOTgzNGIxOWNlYjdkMTE5MmIxMmY1
|
10
|
+
ZGZiMTg4ZTcyNzI3MjhlZjg2OGE0NzU1NjljZjc2NDZjMGU4MGQxMTI0ZTdk
|
11
|
+
M2Q3MDFkYTUyNDE4MjUyZDAwMTA5OGZhZjQ3YTM1MDgzNGM1YjI=
|
12
12
|
data.tar.gz: !binary |-
|
13
|
-
|
14
|
-
|
15
|
-
|
13
|
+
ZTU1OTQ1MDY2NWE4Y2Y5NGRhMzYyNmYyMThhN2RjYmEzZTZhYmM0OWE1NWQz
|
14
|
+
NmFkMDAzMGRkNzE1MGE0NGY1OTNkMjI1NzI2YTJlZjg2NTNmZjg1ZTlkZDIy
|
15
|
+
NmI0MTIyMmI1MDIyZTVkMDZjZTBkMzgyNDJmMWUwYTRhNGFhODE=
|
data/README.md
CHANGED
@@ -17,7 +17,7 @@ As with all gem dependencies, we strongly recommend adding `react-rails` to your
|
|
17
17
|
```ruby
|
18
18
|
# Gemfile
|
19
19
|
|
20
|
-
gem 'react-rails', '~> 0.
|
20
|
+
gem 'react-rails', '~> 0.9.0.0'
|
21
21
|
```
|
22
22
|
|
23
23
|
|
@@ -25,7 +25,7 @@ gem 'react-rails', '~> 0.4.1.0'
|
|
25
25
|
|
26
26
|
### react.js
|
27
27
|
|
28
|
-
In order to use React client-side in your application, you must make sure the browser requests it. One way to do that is to drop `react.js` into `app/assets/javascript/` and by default your
|
28
|
+
In order to use React client-side in your application, you must make sure the browser requests it. One way to do that is to drop `react.js` into `app/assets/javascript/` and by default your application manifest will pick it up. There are downsides to this approach, so we made it even easier. Once you have `react-rails` installed, you can just add a line into your config file (see Configuring) and require react directly in your manifest:
|
29
29
|
|
30
30
|
You can `require` it in your manifest:
|
31
31
|
|
data/lib/react/rails/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: react-rails
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 0.9.0.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Paul O’Shannessy
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date:
|
11
|
+
date: 2014-02-21 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: bundler
|
@@ -86,14 +86,14 @@ dependencies:
|
|
86
86
|
requirements:
|
87
87
|
- - '='
|
88
88
|
- !ruby/object:Gem::Version
|
89
|
-
version: 0.
|
89
|
+
version: 0.9.0
|
90
90
|
type: :runtime
|
91
91
|
prerelease: false
|
92
92
|
version_requirements: !ruby/object:Gem::Requirement
|
93
93
|
requirements:
|
94
94
|
- - '='
|
95
95
|
- !ruby/object:Gem::Version
|
96
|
-
version: 0.
|
96
|
+
version: 0.9.0
|
97
97
|
description: Compile your JSX on demand or precompile for production.
|
98
98
|
email:
|
99
99
|
- paul@oshannessy.com
|