json-iterator/go is not 100% compatible drop-in replacement of encoding/json #229

Activity

1. choleraehyq

   changed the title [-]Missing Compact/Indent/HTMLEscape comparing to encoding/json[/-] [+]json-iterator/go is not 100% compatible drop-in replacement of encoding/json[/+] on Jan 28, 2018
2. taowen commented on Jan 28, 2018

   

   taowen

   on Jan 28, 2018

   Contributor

   More actions

   no one is asking for them

   👎React with 👎35Reacted by Aniruddha Maru, kingeasternsun, Florian Vogt, Elias Daler, Daniel Larsson, Cholerae Hu, ddibiasi, Lee, polynomialspace, Matan Hafuta and 25 more

   😄React with 😄13Reacted by Public Profile, Xargin, Josef Fröhle, sanksons, Gyllsdorff, xuyang2, Luis Gabriel Gómez, temprory, Derek Perkins, Jodi Ivan Lumbantoruan and 3 more
3. veqryn commented on Jul 23, 2018

   

   veqryn

   on Jul 23, 2018

   More actions

   HTML Escaping is supported through the following, I think:

   func jsonIteratorMarshalAddNewLineNoEscapeHTML(v interface{}) ([]byte, error) {
   	buffer := &bytes.Buffer{}
   	encoder := jsonIterator.NewEncoder(buffer)
   	encoder.SetEscapeHTML(false)
   	err := encoder.Encode(v)
   	return buffer.Bytes(), err
   }
4. carbocation commented on Aug 6, 2018

   

   carbocation

   on Aug 6, 2018

   More actions

   The readme says "100% compatibility with standard lib". I think that if this line were removed, this issue could be resolved...

   👍React with 👍29Reacted by Philipp Gillé, Davor Kapša, Florian Vogt, Elias Daler, ZC, Maxim, Daniel Martí, Cholerae Hu, Lee, Matan Hafuta and 19 more

   😄React with 😄23Reacted by Yang Yang, Ethan, Peng Tan, Brendan Walters, zc, Miron Yanovskiy, Christian Hansen, Command M, Maxim, simon and 13 more
5. shatil commented on Oct 20, 2018

   

   shatil

   on Oct 20, 2018

   More actions

   #313 relates to this. jsoniter doesn't support the Umarshaler interface: https://golang.org/pkg/encoding/json/#Unmarshaler
6. jszwedko commented on Apr 13, 2020

   

   jszwedko

   on Apr 13, 2020

   Last edited by jszwedko

   More actions

   I agree that the README should be updated to convey which parts are not compatible with encoding/json and not say "100% compatible". There are a couple functions missing from the Decoder type:

           func (dec *Decoder) InputOffset() int64
           func (dec *Decoder) Token() (Token, error)
   

   I had wanted to try out switching to json-iterator/go, but our code currently depends on these functions for one of our packages that does stream processing of documents and I was surprised to find them missing given the claim of drop-in compatibility.

   👍React with 👍11Reacted by Andrei Dascalu, GalvinGao, Matan Hafuta, Saif Ali Khan, Vladislav Yarmak, Big Phil, bittrainee, Mahmudur Rahman, Terence, Furkan Türkal and 1 more
7. Dentrax commented on Apr 18, 2023

   

   Dentrax

   on Apr 18, 2023

   Last edited by Dentrax

   More actions

   no one is asking for them

   Any updates on this? I'm asking. 👋 I'm just hit this issue. 🙈
8. damnever commented on May 5, 2023

   

   damnever

   on May 5, 2023

   More actions

   Another issue: #657
9. CHN-STUDENT commented on Sep 27, 2024

   

   CHN-STUDENT

   on Sep 27, 2024

   More actions

   Hey，how can i export '&' char on my json by using json-iterator,could every one give me advice?