The short answer: Yes but is not recommended. The long answer: It depends on what you call valid… [ECMA-404][1] “The JSON Data Interchange Syntax” doesn’t say anything about duplicated names (keys). However, [RFC 8259][2] “The JavaScript Object Notation (JSON) Data Interchange Format” says: The names within an object SHOULD be unique. In this context SHOULD … Read more
These are some quick shots at this to show a few different ways. They are by no means “complete” and as a disclaimer, I don’t think it’s a good idea to do it like this. Also the code isn’t too clean since I just typed it together rather quickly. Also as a note: Of course … Read more
The question is asking for fields to be dynamically selected based on the caller-provided list of fields. This isn’t possible to be done with the statically-defined json struct tag. If what you want is to always skip a field to json-encode, then of course use json:”-” to ignore the field. (Note also that this is … Read more
Well, you can achieve that with Jackson, too. (and it seems to be more comfortable since you were considering using jackson). Use ObjectMapper‘s convertValue method: final ObjectMapper mapper = new ObjectMapper(); // jackson’s objectmapper final MyPojo pojo = mapper.convertValue(map, MyPojo.class); No need to convert into JSON string or something else; direct conversion does much faster.
You need to export the User.name field so that the json package can see it. Rename the name field to Name. package main import ( “fmt” “encoding/json” ) type User struct { Name string } func main() { user := &User{Name: “Frank”} b, err := json.Marshal(user) if err != nil { fmt.Println(err) return } fmt.Println(string(b)) … Read more
Yes, you need quotation marks. This is to make it simpler and to avoid having to have another escape method for javascript reserved keywords, ie {for:”foo”}.
It really depends on what your input is. If you look at the implementation of the Decode method of json.Decoder, it buffers the entire JSON value in memory before unmarshalling it into a Go value. So in most cases it won’t be any more memory efficient (although this could easily change in a future version … Read more
Follow the below code : if let path = NSBundle.mainBundle().pathForResource(“test”, ofType: “json”) { if let jsonData = NSData(contentsOfFile: path, options: .DataReadingMappedIfSafe, error: nil) { if let jsonResult: NSDictionary = NSJSONSerialization.JSONObjectWithData(jsonData, options: NSJSONReadingOptions.MutableContainers, error: nil) as? NSDictionary { if let persons : NSArray = jsonResult[“person”] as? NSArray { // Do stuff } } } } The … Read more
By pretty-print, I assume you mean indented, like so { “data”: 1234 } rather than {“data”:1234} The easiest way to do this is with MarshalIndent, which will let you specify how you would like it indented via the indent argument. Thus, json.MarshalIndent(data, “”, ” “) will pretty-print using four spaces for indentation.
OP here (I am answering this question after two years, the post made by Daniel Cerecedo was not bad at a time, but the web services are developing very fast) After three years of full-time software development (with focus also on software architecture, project management and microservice architecture) I definitely choose the second way (but … Read more