log-analyser 0.1.3.pre.documentation.20201108212148 → 0.1.3.pre.documentation.20201108213409
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 +4 -4
- data/README.md +9 -6
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: b130e3448b5bce64a194ad4843b9d7712e1cee00821086c8d207b187091784ef
|
|
4
|
+
data.tar.gz: 59933e1912afc0632d6304fe59ef74370a6bf95114773bd7883b273292c693c5
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 6631b545a1ce34e7a0c291b043c9741dbfd2099aaf4c7129dcde40edc0511905509ac0fa4b88c25d77d72672808e2e2a075e340aaa6863a126be3cbc2f973466
|
|
7
|
+
data.tar.gz: 5c96d28a31b7b40f022acd0a09ce143e76e4df0788636f4edb15dbe0c659e65ee80e691d9e7b17287299e226356e2f1ffd13d6c60a874239ae69f0d7f58a51eb
|
data/README.md
CHANGED
|
@@ -169,7 +169,7 @@ $ bundle install
|
|
|
169
169
|
|
|
170
170
|
And the world is your oyster...
|
|
171
171
|
|
|
172
|
-
You can also run
|
|
172
|
+
You can also run `$ bundle exec console` for an interactive prompt that will allow you to experiment.
|
|
173
173
|
|
|
174
174
|
To install this gem onto your local machine, run `$ bundle exec rake install`.
|
|
175
175
|
To release a new version, update the version number in `version.rb`, and then run `$ bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
|
|
@@ -184,15 +184,15 @@ Use `$ bundle exec rake rubocop` to run the checks.
|
|
|
184
184
|
|
|
185
185
|
[](https://coveralls.io/github/DMazzei/log-analyser?branch=master)
|
|
186
186
|
|
|
187
|
-
Use `$ bundle exec rake spec:all` to run all the tests.
|
|
187
|
+
Use `$ bundle exec rspec` or `$ bundle exec rake spec:all` to run all the tests.
|
|
188
188
|
|
|
189
189
|
:white_check_mark: To run only unit-tests
|
|
190
190
|
|
|
191
|
-
$bundle exec rake spec:unit
|
|
191
|
+
$ bundle exec rake spec:unit
|
|
192
192
|
|
|
193
193
|
:white_check_mark: To run only integration tests
|
|
194
194
|
|
|
195
|
-
$bundle exec rake spec:integration
|
|
195
|
+
$ bundle exec rake spec:integration
|
|
196
196
|
|
|
197
197
|
The test coverage is handled by `rspec`, `simplecov` and `coveralls`.
|
|
198
198
|
Status and coverage history can be checked [here](https://coveralls.io/github/DMazzei/log-analyser).
|
|
@@ -215,8 +215,11 @@ The whole deployment process will finish by building and tagging a new gem versi
|
|
|
215
215
|
Bug reports and pull requests are welcome on GitHub at https://github.com/DMazzeig/log-analyser.
|
|
216
216
|
|
|
217
217
|
## Next Steps
|
|
218
|
-
|
|
219
|
-
-
|
|
218
|
+
|
|
219
|
+
- One conundrum faced that can be reviewed, deciding between:
|
|
220
|
+
* reading the file whilst aggregation data, preserving memory - e.g. using `Set`;
|
|
221
|
+
* loading data into memory and leaving aggregation and count to be dealt later, gaining flexibility and performance;
|
|
222
|
+
- Extend the accepted logfile format;
|
|
220
223
|
- Add more options for sorting and filtering;
|
|
221
224
|
- Automate library version bump up;
|
|
222
225
|
|