README.md in memolog-0.3.5 vs README.md in memolog-0.4.0

- old
+ new

@@ -24,24 +24,24 @@ Use this example during application initialization process (this example implement default values): ```ruby Memolog.configure do |config| config.debug = false - config.formatter = ::Memolog::Formatter.new + config.formatter = ::Logger::Formatter.new config.middlewares = %i[rails sidekiq] + config.log_json = false config.log_size_limit = 50_000 - config.uuid_callable = -> { SecureRandom.uuid } end Memolog.init_middlewares! ``` Available options are: - `debug` - set it to true if you need to leave Memolog.dump result outside `Memolog.run {}` block. - `formatter` - setup your own formatter. - `middlewares` - define here what you want to initialize in `#init_middlewares!` call. +- `log_json` - `#dump` will try to parse dump with `JSON.parse()`. Default is `false` - `log_size_limit` - max log length in `#dump`. -- `uuid_callable` - Memolog add unique value to logs, here you can redefine uuid generation. If you want to apply Sentry monkey patch that call `Memolog.dump` before `Sentry.capture_exception` and `Sentry.capture_message` you can implement it via this code: ```ruby