accept a struct / array of structs about ojg HOT 4 CLOSED

Both converting a struct to a []byte or string is done using reflection or by having the struct implement an interface. There are some examples in the write unit tests. If they are not enough I'd be glad to add some more complex ones.

from ojg.

hmmm, I only want to generate json and write it later. Is there another way not using write?
(Reason is that i want to store the generated json in cache so it can skip everything when it's in the cache)

I have this as a test:

	data := make(map[string]interface{}, 2)
	data["success"] = true
	model := testModel{}
	model.Field1 = "F1"
	model.Field2 = "F2"
	data["record"] = model
	result := presenters.OutputJSONoj(resp, data)
	log.Printf("JSON_test.go:66 result %s\n", string(result))

And this is the output:
2020/10/16 09:00:12 JSON_test.go:66 result {"success":true,"record":"{F1 F2}"}
Which is missing the 2 fieldnames, which I thing are necessary in the frontend.

and with doing this "trick"

// the OutputJSONoj part
	var bbuf strings.Builder
	err := oj.Write(&bbuf, data)
	if err != nil {
		libError.FatalError(err)
	}

	b := []byte(bbuf.String())

this is slower than the normal json variant :-(

from ojg.

I'm not sure what you are trying to achieve with that. It would be far simpler to just use oj.JSON(data). In your example, strings.Builder will never return an error on Write(). You can check the golang code. If you just want to feel comfortable by checking for errors you can try the marshal branch I suggested in your other issue #25 . The oj.Marshal() function does return both a []byte and an error. An error is returned if you try to encode un-encodeable values such as a function or chan. That way you have a reason to check for errors.

from ojg.

I think this should be closed as well. Do you agree?

from ojg.