exodus 1.0.5 → 1.0.6
Sign up to get free protection for your applications and to get access to all the features.
- data/CHANGELOG.md +4 -0
- data/README.md +1 -3
- data/lib/exodus/helpers/text_formatter.rb +3 -1
- data/lib/exodus/version.rb +1 -1
- metadata +2 -2
data/CHANGELOG.md
CHANGED
data/README.md
CHANGED
@@ -1,9 +1,7 @@
|
|
1
1
|
Exodus - a migration framework for MongoDb
|
2
2
|
=============
|
3
3
|
|
4
|
-
#
|
5
|
-
|
6
|
-
## A migration Framework for a schemaless database ??
|
4
|
+
# A migration Framework for a schemaless database?
|
7
5
|
|
8
6
|
After working with Mongo for long time now I can tell you working with a schemaless database does not mean you will never need any migrations. Within the same collection Mongo allows to have documents with a complete different structure, however in some case is you might want to keep data consistency; Especially when your code is live in production and used by millions of users.
|
9
7
|
|
@@ -21,7 +21,9 @@ module Exodus
|
|
21
21
|
|
22
22
|
paragraphes.each_with_index do |sentences, paragraph_number|
|
23
23
|
sentences.each_with_index do |sentence, column|
|
24
|
-
|
24
|
+
words = sentence.gsub('=>', ' => ').split(' ') || ''
|
25
|
+
|
26
|
+
if sentence.size > space_number && (words).size > 1
|
25
27
|
new_sentence = ""
|
26
28
|
words.each_with_index do |word, nb_word|
|
27
29
|
if new_sentence.size + word.size < space_number
|
data/lib/exodus/version.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: exodus
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.0.
|
4
|
+
version: 1.0.6
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -9,7 +9,7 @@ authors:
|
|
9
9
|
autorequire:
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
|
-
date: 2013-
|
12
|
+
date: 2013-08-04 00:00:00.000000000 Z
|
13
13
|
dependencies:
|
14
14
|
- !ruby/object:Gem::Dependency
|
15
15
|
name: mongo_mapper
|