Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / cnuernber/charred issues and pull requests

#32 - Fixes #31 regression introduced in 1.035

Pull Request - State: closed - Opened by FieryCod 27 days ago - 1 comment

#31 - Newlines no longer escaped in 1.035

Issue - State: closed - Opened by dekelpilli 28 days ago - 1 comment

#30 - [Fix #25] Port DJSON-61 optimization to charred

Pull Request - State: closed - Opened by FieryCod about 1 month ago

#29 - Escaping double quotes not working if they appear right after `\n`

Issue - State: closed - Opened by carlosgeos 3 months ago - 2 comments

#28 - exception on writing maps where a key is a map

Issue - State: open - Opened by flyingmachine 4 months ago - 1 comment

#27 - re-use this for single row parsing

Issue - State: open - Opened by behrica 4 months ago - 1 comment

#26 - Error with CSV multi-line comments

Issue - State: closed - Opened by jlesquembre about 1 year ago

#25 - Faster JSON writing

Issue - State: closed - Opened by cnuernber about 1 year ago - 2 comments

#24 - Add allowlist/blocklist

Pull Request - State: closed - Opened by otfrom over 1 year ago - 1 comment

#23 - Clarify what is the default of `:eof-value` in `read-json-supplier`

Pull Request - State: closed - Opened by carlosgeos over 1 year ago - 1 comment

#22 - `[needed example]` streaming processing

Issue - State: closed - Opened by harold over 1 year ago - 1 comment

#21 - :close-writer? should probably not be true by default

Issue - State: closed - Opened by kanwei over 1 year ago - 9 comments

#20 - fix charred.api/read-json-supplier :value-fn description with respect to elision

Pull Request - State: closed - Opened by stanislas over 1 year ago - 1 comment

#19 - Column quoting behavior. `read-csv` vs `read-csv-supplier`

Issue - State: closed - Opened by carlosgeos almost 2 years ago - 4 comments

#18 - Fix Instant/j.u.Date json serialization #17

Pull Request - State: closed - Opened by kawas44 almost 2 years ago - 1 comment

#17 - Serialization of Instant is not consistent with other libs

Issue - State: closed - Opened by kawas44 almost 2 years ago - 1 comment

#16 - Fix docstring for write-json to match code about :indent-str

Pull Request - State: closed - Opened by matusfi almost 2 years ago - 1 comment

#15 - Extending to YAML or EDN - any interest?

Issue - State: open - Opened by cnuernber almost 2 years ago - 3 comments

#14 - Allow for options map in read-json

Pull Request - State: closed - Opened by FiV0 about 2 years ago

#13 - Make passing options more convenient

Issue - State: closed - Opened by FiV0 about 2 years ago - 3 comments

#12 - Fantastic csv error message

Issue - State: closed - Opened by cnuernber about 2 years ago - 1 comment

#11 - RuntimeException: Unread too far - current buffer empty

Issue - State: closed - Opened by hjrnunes over 2 years ago - 1 comment

#10 - Fixes #9, adding identifiable exceptions for parse/encode errors.

Pull Request - State: closed - Opened by ryantate over 2 years ago - 1 comment

#9 - Feature request: Identifiable exceptions for parse errors

Issue - State: closed - Opened by ryantate over 2 years ago - 6 comments

#7 - Unhandled java.io.EOFException

Issue - State: closed - Opened by lhrb over 2 years ago - 10 comments

#6 - Issue when parsing to string when data includes a set

Issue - State: closed - Opened by domparry over 2 years ago - 6 comments

#5 - Crash if csv is ending with carriage-return

Issue - State: closed - Opened by maxthoursie over 2 years ago - 3 comments

#4 - differing whitespace behavior vs data.json/cheshire

Issue - State: closed - Opened by edporras almost 3 years ago - 2 comments

#3 - About default behaviour of keywords serialisation

Issue - State: closed - Opened by BrunoBonacci almost 3 years ago - 3 comments

#2 - Empty strings are coerced to nil by default

Issue - State: closed - Opened by p-himik almost 3 years ago - 1 comment

#1 - Feature: lazy parsing

Issue - State: closed - Opened by bsless almost 3 years ago - 2 comments