multi_json 1.20.1 → 1.21.1

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.
Files changed (21) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +115 -38
  3. data/lib/multi_json/adapter.rb +62 -10
  4. data/lib/multi_json/adapter_error.rb +1 -1
  5. data/lib/multi_json/adapter_selector.rb +34 -14
  6. data/lib/multi_json/adapters/fast_jsonparser.rb +12 -10
  7. data/lib/multi_json/adapters/json_gem.rb +2 -19
  8. data/lib/multi_json/adapters/oj.rb +6 -6
  9. data/lib/multi_json/adapters/oj_common.rb +1 -1
  10. data/lib/multi_json/adapters/yajl.rb +1 -1
  11. data/lib/multi_json/concurrency.rb +7 -7
  12. data/lib/multi_json/deprecated.rb +26 -23
  13. data/lib/multi_json/options.rb +97 -23
  14. data/lib/multi_json/options_cache/mutex_store.rb +1 -1
  15. data/lib/multi_json/options_cache.rb +7 -7
  16. data/lib/multi_json/parse_error.rb +1 -1
  17. data/lib/multi_json/version.rb +6 -6
  18. data/lib/multi_json.rb +105 -53
  19. metadata +5 -7
  20. data/CHANGELOG.md +0 -312
  21. data/CONTRIBUTING.md +0 -53
data/CONTRIBUTING.md DELETED
@@ -1,53 +0,0 @@
1
- ## Contributing
2
- In the spirit of [free software][free-sw], **everyone** is encouraged to help
3
- improve this project.
4
-
5
- [free-sw]: http://www.fsf.org/licensing/essays/free-sw.html
6
-
7
- Here are some ways *you* can contribute:
8
-
9
- * by using alpha, beta, and prerelease versions
10
- * by reporting bugs
11
- * by suggesting new features
12
- * by writing or editing documentation
13
- * by writing tests
14
- * by writing code (**no patch is too small**: fix typos, add comments, clean up
15
- inconsistent whitespace)
16
- * by refactoring code
17
- * by closing [issues][]
18
- * by reviewing patches
19
-
20
- [issues]: https://github.com/sferik/multi_json/issues
21
-
22
- ## Submitting an Issue
23
- We use the [GitHub issue tracker][issues] to track bugs and features. Before
24
- submitting a bug report or feature request, check to make sure it hasn't
25
- already been submitted. When submitting a bug report, please include a
26
- [Gist][gist] that includes a stack trace and any details that may be necessary
27
- to reproduce the bug, including your gem version, Ruby version, and operating
28
- system. Ideally, a bug report should include a pull request with failing tests.
29
-
30
- [gist]: https://gist.github.com/
31
-
32
- ## Submitting a Pull Request
33
- 1. [Fork the repository.][fork]
34
- 2. [Create a topic branch.][branch]
35
- 3. Add tests for your unimplemented feature or bug fix.
36
- 4. Run `bundle exec rake test`. If your tests pass, return to step 3.
37
- 5. Implement your feature or bug fix.
38
- 6. Run `bundle exec rake test`. If your tests fail, return to step 5.
39
- 7. Run `open coverage/index.html`. If your changes are not completely covered
40
- by your tests, return to step 3.
41
- 8. Run `bundle exec rake mutant` and kill any surviving mutants.
42
- 9. Run `bundle exec rake lint` and fix any offenses.
43
- 10. Run `bundle exec rake yardstick` and add any missing documentation.
44
- 11. Run `bundle exec rake steep` and ensure that the code typechecks.
45
- 12. Add, commit, and push your changes.
46
- 13. [Submit a pull request][pr] that summarizes *what* changes you made and
47
- *why* you made them. If you made any significant decisions along the way,
48
- describe the options you considered and how you thought about the
49
- tradeoffs.
50
-
51
- [fork]: http://help.github.com/fork-a-repo/
52
- [branch]: http://learn.github.com/p/branching.html
53
- [pr]: http://help.github.com/send-pull-requests/