karafka 1.1.0 → 1.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 26ee2938706de62609da9faf4179b3071fdc9e62
-  data.tar.gz: eedc149b1ade99a21d82f32ad3ec9009b065cc89
+  metadata.gz: 1fcea5db98bb786e35298cda7dcfc34354935106
+  data.tar.gz: 8da4bad16ba1d23a04b6bfc6906d8432ff3d715c
 SHA512:
-  metadata.gz: 2e25b2453563d9330955248307eee910147899fefb15bc197313f79012c132f0970fede7f0a0fd50b6966267c9d7d48f82f50b75fea927baa8c01bf68ebee305
-  data.tar.gz: 902fd68ad24eb5400976d9f6b3cc5d955617a70e0b14186e2b27e8292fcff2d59aa013231834ad679c9694eebd6809589cf98715151d89a1637d6e71e2f5a14e
+  metadata.gz: c775dc7525a5e3f0252b5d5fb90f37d31636d2aeec99de936650ff6de6ec45c93383b111bd600d2cc190808e3b5f941dd619d8c5d51ad95c53852217df38184f
+  data.tar.gz: c891f17541b7298ac7e9e310d3d16a1e3464d365db34fcfb461109ddb6d03e3f499ccc1bd1886539d62d2451754adf4a7e9a4763324b5d46bcda680ca60ed358

data/CHANGELOG.md

@@ -1,6 +1,9 @@
 # Karafka framework changelog
 
-## 1.1.0 Unreleased
+## 1.1.1
+- #253 - Allow providing a global per app parser in config settings
+
+## 1.1.0
 - Gem bump
 - Switch from Celluloid to native Thread management
 - Improved shutdown process
@@ -14,7 +17,7 @@
 - Fixed accessibility of ```#params_batch``` from the outside of the controller
 - connection_pool config options are no longer required
 - celluloid config options are no longer required
-- ```#perform``` is not renamed to ```#consume``` with warning level on using the old one (deprecated)
+- ```#perform``` is now renamed to ```#consume``` with warning level on using the old one (deprecated)
 - #235 - Rename perform to consume
 - Upgrade to ruby-kafka 0.5
 - Due to redesign of Waterdrop concurrency setting is no longer needed
@@ -23,6 +26,7 @@
 - Renamed ```batch_consuming``` option to ```batch_fetching``` as it is not a consumption (with processing) but a process of fetching messages from Kafka. The messages is considered consumed, when it is processed.
 - Renamed ```batch_processing``` to ```batch_consuming``` to resemble Kafka concept of consuming messages.
 - Renamed ```after_received``` to ```after_fetched``` to normalize the naming conventions.
+- Responders support the per topic ```async``` option.
 
 ## 1.0.1
 - #210 - LoadError: cannot load such file -- [...]/karafka.rb

data/CONTRIBUTING.md

@@ -9,7 +9,6 @@ We welcome any type of contribution, not only code. You can help with
 - **Marketing**: writing blog posts, howto's, printing stickers, ...
 - **Community**: presenting the project at meetups, organizing a dedicated meetup for the local community, ...
 - **Code**: take a look at the [open issues](issues). Even if you can't write code, commenting on them, showing that you care about a given issue matters. It helps us triage them.
-- **Money**: we welcome financial contributions in full transparency on our [open collective](https://opencollective.com/karafka).
 
 ## Your First Contribution
 
@@ -21,13 +20,13 @@ Any code change should be submitted as a pull request. The description should ex
 
 ## Code review process
 
-The bigger the pull request, the longer it will take to review and merge. Try to break down large pull requests in smaller chunks that are easier to review and merge.
-It is also always helpful to have some context for your pull request. What was the purpose? Why does it matter to you?
+Each pull request must pass all the rspec specs and meet our quality requirements.
 
-## Financial contributions
+To check if everything is as it should be, we use [Coditsu](https://coditsu.io) that combines multiple linters and code analyzers for both code and documentation. Once you're done with your changes, submit a pull request.
 
-We also welcome financial contributions in full transparency on our [open collective](https://opencollective.com/karafka).
-Anyone can file an expense. If the expense makes sense for the development of the community, it will be "merged" in the ledger of our open collective by the core contributors and the person who filed the expense will be reimbursed.
+Coditsu will automatically check your work against our quality standards. You can find your commit check results on the [builds page](https://app.coditsu.io/karafka/commit_builds) of Karafka organization.
+
+[![coditsu](https://coditsu.io/assets/quality_bar.svg)](https://app.coditsu.io/karafka/commit_builds)
 
 ## Questions
 

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    karafka (1.1.0)
+    karafka (1.1.1)
       activesupport (>= 5.0)
       dry-configurable (~> 0.7)
       dry-validation (~> 0.11)
@@ -64,7 +64,7 @@ GEM
     minitest (5.10.3)
     multi_json (1.12.2)
     null-logger (0.1.4)
-    rake (12.2.1)
+    rake (12.3.0)
     require_all (1.4.0)
     rspec (3.7.0)
       rspec-core (~> 3.7.0)
@@ -108,4 +108,4 @@ DEPENDENCIES
   waterdrop
 
 BUNDLED WITH
-   1.15.4
+   1.16.0

data/README.md

@@ -62,26 +62,17 @@ Karafka framework and Karafka team are __not__ related to Kafka streaming servic
 * [Karafka Travis CI](https://travis-ci.org/karafka/karafka)
 * [Karafka Coditsu](https://app.coditsu.io/karafka/repositories/karafka)
 
-## Note on Patches/Pull Requests
+## Note on contributions
 
-Fork the project.
-Make your feature addition or bug fix.
-Add tests for it. This is important so we don't break it in a future versions unintentionally.
-Commit, do not mess with Rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull). Send me a pull request. Bonus points for topic branches.
+First, thank you for considering contributing to Karafka! It's people like you that make the open source community such a great community!
 
-[![coditsu](https://coditsu.io/assets/quality_bar.svg)](https://app.coditsu.io/karafka/repositories/karafka)
+Each pull request must pass all the rspec specs and meet our quality requirements.
 
-Each pull request must pass our quality requirements. To check if everything is as it should be, we use [Coditsu](https://coditsu.io) that combines multiple linters and code analyzers for both code and documentation.
+To check if everything is as it should be, we use [Coditsu](https://coditsu.io) that combines multiple linters and code analyzers for both code and documentation. Once you're done with your changes, submit a pull request.
 
-Unfortunately, it does not yet support independent forks, however you should be fine by looking at what we require.
+Coditsu will automatically check your work against our quality standards. You can find your commit check results on the [builds page](https://app.coditsu.io/karafka/commit_builds) of Karafka organization.
 
-Please run:
-
-```bash
-bundle exec rspec
-```
-
-to check if everything is in order. After that you can submit a pull request.
+[![coditsu](https://coditsu.io/assets/quality_bar.svg)](https://app.coditsu.io/karafka/commit_builds)
 
 ## Contributors
 

data/lib/karafka/base_responder.rb

@@ -92,7 +92,7 @@ module Karafka
     # @param parser_class [Class] parser class that we can use to generate appropriate string
     #   or nothing if we want to default to Karafka::Parsers::Json
     # @return [Karafka::BaseResponder] base responder descendant responder
-    def initialize(parser_class = Karafka::Parsers::Json)
+    def initialize(parser_class = Karafka::App.config.parser)
       @parser_class = parser_class
       @messages_buffer = {}
     end

data/lib/karafka/routing/topic.rb

@@ -39,12 +39,6 @@ module Karafka
         @responder ||= Karafka::Responders::Builder.new(controller).build
       end
 
-      # @return [Class] Parser class (not instance) that we want to use to unparse Kafka messages
-      # @note If not provided - will use Json as default
-      def parser
-        @parser ||= Karafka::Parsers::Json
-      end
-
       Karafka::AttributesMap.topic.each do |attribute|
         config_retriever_for(attribute)
       end

data/lib/karafka/setup/config.rb

@@ -34,6 +34,8 @@ module Karafka
       #   - #incoming - for remapping from the incoming message to our internal format
       #   - #outgoing - for remapping from internal topic name into outgoing message
       setting :topic_mapper, -> { Routing::TopicMapper }
+      # Default parser for parsing and unparsing incoming and outgoing data
+      setting :parser, -> { Karafka::Parsers::Json }
       # If batch_fetching is true, we will fetch kafka messages in batches instead of 1 by 1
       # @note Fetching does not equal consuming, see batch_consuming description for details
       setting :batch_fetching, true

data/lib/karafka/version.rb

@@ -3,5 +3,5 @@
 # Main module namespace
 module Karafka
   # Current Karafka version
-  VERSION = '1.1.0'
+  VERSION = '1.1.1'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: karafka
 version: !ruby/object:Gem::Version
-  version: 1.1.0
+  version: 1.1.1
 platform: ruby
 authors:
 - Maciej Mensfeld
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-11-07 00:00:00.000000000 Z
+date: 2017-11-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -163,7 +163,6 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".console_irbrc"
-- ".github/ISSUE_TEMPLATE.md"
 - ".gitignore"
 - ".rspec"
 - ".ruby-gemset"

data/.github/ISSUE_TEMPLATE.md

@@ -1,2 +0,0 @@
-<!-- Love karafka? Please consider supporting our collective:
-👉  https://opencollective.com/karafka/donate -->