tolken 0.3.0 → 0.3.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/.rubocop.yml +1 -0
- data/Gemfile.lock +1 -1
- data/README.md +4 -3
- data/lib/tolken/version.rb +1 -1
- data/tolken.gemspec +8 -10
- metadata +10 -12
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: d6bba5215d5b80b01dff93c1e144b211c5dbb20b26efbb4aa8f4b31252ca1dbc
|
|
4
|
+
data.tar.gz: 42c0e38832a55ea0afce7b7e29bda8b8cdeafad90de78c1b67b21e25f45efe7c
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 2f4401319f42c32446a82380d2769adb5f0eaa4bb8c273ad2449c2bf2c6a989d721445c5a4785b189beeff401ce1071361eb82087515a024577cf66ec1857cc0
|
|
7
|
+
data.tar.gz: 75382baf1e07e5e02a59c60f168f1d3c01c32162f72d63886b8a63ecdd3f598767cbcb141139d408977921b20cf22a972dc0f87f7b1d2fb7c718f785d77466ff
|
data/.rubocop.yml
CHANGED
data/Gemfile.lock
CHANGED
data/README.md
CHANGED
|
@@ -1,8 +1,9 @@
|
|
|
1
1
|
# Tolken
|
|
2
|
-
|
|
2
|
+
Straightforward Rails database translations using psql jsonb
|
|
3
3
|
|
|
4
|
-
Tolken's API is more verbose than most similar gems. The idea is that you should be aware of when you're dealing with translatable fields and what language you're interested in in any given moment.
|
|
4
|
+
Tolken's API is more verbose than most similar gems. The idea is that you should be aware of when you're dealing with translatable fields and what language you're interested in in any given moment. In tolken a translatable field is just a Ruby hash which makes it easy to reason about. See *Usage* for details.
|
|
5
5
|
|
|
6
|
+
[](https://badge.fury.io/rb/tolken)
|
|
6
7
|
[](https://travis-ci.org/varvet/tolken)
|
|
7
8
|
[](https://codeclimate.com/github/varvet/tolken/maintainability)
|
|
8
9
|
[](https://codeclimate.com/github/varvet/tolken/test_coverage)
|
|
@@ -134,7 +135,7 @@ The specs for [translates](spec/tolken/translates_spec.rb) is a good resource of
|
|
|
134
135
|
## Development
|
|
135
136
|
|
|
136
137
|
### Native dependencies
|
|
137
|
-
You need to have
|
|
138
|
+
You need to have postgresql installed on your system. This can be done on Mac OS with `brew install postgresql`.
|
|
138
139
|
|
|
139
140
|
### Ruby setup
|
|
140
141
|
After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
|
data/lib/tolken/version.rb
CHANGED
data/tolken.gemspec
CHANGED
|
@@ -7,17 +7,15 @@ require "tolken/version"
|
|
|
7
7
|
Gem::Specification.new do |spec|
|
|
8
8
|
spec.name = "tolken"
|
|
9
9
|
spec.version = Tolken::VERSION
|
|
10
|
-
spec.authors = ["Nicklas Ramhöj, Julia Friberg"]
|
|
11
|
-
spec.email = ["nicklas.ramhoj@varvet.com, julia.friberg@varvet.com"]
|
|
10
|
+
spec.authors = ["Nicklas Ramhöj", "Julia Friberg"]
|
|
11
|
+
spec.email = ["nicklas.ramhoj@varvet.com", "julia.friberg@varvet.com"]
|
|
12
12
|
|
|
13
|
-
spec.summary = "
|
|
14
|
-
spec.description =
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
quickly becomes a liability. In Tolken a translatable field is just a Ruby hash which makes it easy to reason about.
|
|
20
|
-
"""
|
|
13
|
+
spec.summary = "Straightforward Rails database translations using psql jsonb"
|
|
14
|
+
spec.description = %q{
|
|
15
|
+
Tolken's API is more verbose than most similar gems. The idea is that you should be aware of when you're dealing with
|
|
16
|
+
translatable fields and what language you're interested in in any given moment. In tolken a translatable field is just a
|
|
17
|
+
Ruby hash which makes it easy to reason about.
|
|
18
|
+
}
|
|
21
19
|
spec.homepage = "https://github.com/varvet/tolken"
|
|
22
20
|
spec.license = "MIT"
|
|
23
21
|
|
metadata
CHANGED
|
@@ -1,10 +1,11 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: tolken
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.3.
|
|
4
|
+
version: 0.3.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
|
-
- Nicklas Ramhöj
|
|
7
|
+
- Nicklas Ramhöj
|
|
8
|
+
- Julia Friberg
|
|
8
9
|
autorequire:
|
|
9
10
|
bindir: exe
|
|
10
11
|
cert_chain: []
|
|
@@ -164,16 +165,13 @@ dependencies:
|
|
|
164
165
|
- - "~>"
|
|
165
166
|
- !ruby/object:Gem::Version
|
|
166
167
|
version: '2.0'
|
|
167
|
-
description: "\n
|
|
168
|
-
|
|
169
|
-
|
|
170
|
-
|
|
171
|
-
\ gems such as Globalize, while it might fit some projects we've found that the
|
|
172
|
-
magic that starts out as a convenience\n quickly becomes a liability. In Tolken
|
|
173
|
-
a translatable field is just a Ruby hash which makes it easy to reason about.\n
|
|
174
|
-
\ "
|
|
168
|
+
description: "\n Tolken's API is more verbose than most similar gems. The idea
|
|
169
|
+
is that you should be aware of when you're dealing with\n translatable fields
|
|
170
|
+
and what language you're interested in in any given moment. In tolken a translatable
|
|
171
|
+
field is just a\n Ruby hash which makes it easy to reason about.\n "
|
|
175
172
|
email:
|
|
176
|
-
- nicklas.ramhoj@varvet.com
|
|
173
|
+
- nicklas.ramhoj@varvet.com
|
|
174
|
+
- julia.friberg@varvet.com
|
|
177
175
|
executables: []
|
|
178
176
|
extensions: []
|
|
179
177
|
extra_rdoc_files: []
|
|
@@ -218,5 +216,5 @@ rubyforge_project:
|
|
|
218
216
|
rubygems_version: 2.7.3
|
|
219
217
|
signing_key:
|
|
220
218
|
specification_version: 4
|
|
221
|
-
summary:
|
|
219
|
+
summary: Straightforward Rails database translations using psql jsonb
|
|
222
220
|
test_files: []
|