


I have several JSONs with the same structure. Their objects are arrays of objects. How can I append these arrays into an array?
What I want to do:
I want to send multiple get requests to this url:
https://catalog.wb.ru/brands/m/catalog?page=1&limit=300&brand=5786&dest=-1257786&sort=pricedown
Then collect all the data inside the "product" object. The value of key "page" is automatically incremented to get data for all pages.
Actually, I'm not really sure if I really need to write a json to send it to the frontend. Maybe it would be better to send a different request when I receive a new response in the for loop?
what did I do:
Made the correct structure. With a single request everything works fine.
Created requestbodybytes []byte
and productsbytes []byte
so that they can be combined with []bytes## in
ioutil.readall # Append together.
Printing the length of
requestbodybytes I see that it expands with each request, but after I unmarshal it I see empty structures in the output.
type response. But what if I need a slice of
product structs consisting of
type response 'product' objects in multiple json s?
requestbodybytes inside the for loop to use it to stop sending requests because the server will give a 200 code and empty json when there is no information on the page.
const URL = "https://catalog.wb.ru/brands/m/catalog?page=%d&limit=300&brand=5786&dest=-1257786&sort=pricedown" type Response struct { Data struct { Products []Product `json:"products"` } `json:"data"` } type Product struct { ID int `json:"id"` Name string `json:"name"` Price int `json:"priceU"` Rating float32 `json:"reviewRating"` Sale int `json:"sale"` New bool `json:"isNew"` } func main() { var response Response var products Response //Also tried to make it []Response var ProductsBytes []byte for i := 1; ; i++ { resp, err := http.Get(fmt.Sprintf(URL, i)) if err != nil { fmt.Printf("#1 Error: %s", err) } defer resp.Body.Close() bytes, err := ioutil.ReadAll(resp.Body) var requestBodyBytes []byte requestBodyBytes = append(requestBodyBytes, bytes...) ProductsBytes = append(ProductsBytes, bytes...) json.Unmarshal(requestBodyBytes, &response) fmt.Println(resp.Status) fmt.Printf("\nSlice from page #%d\nLength of bytes: %d\n", i, len(bytes)) fmt.Printf("Length of finalResult: %d\n", len(requestBodyBytes)) if len(response.Data.Products) == 0 { fmt.Println("There's no more data") break } } json.Unmarshal(ProductsBytes, &products) fmt.Println(response) fmt.Println(products) fmt.Println(len(products)) }
Correct answer
There is no reason to collect all raw response bytes. Just unmarshal each response individually and append each page's products to some slice that contains all products. Also, calling
defer resp.body.close() inside a loop may not be what you want. Deferred statements are only executed after the loop ends, so the connection cannot be reused for requests. Extracting the loop body into its own function makes this clearer:
package main import ( "encoding/json" "errors" "fmt" "log" "net/http" ) const URL = "https://catalog.wb.ru/brands/m/catalog?page=%d&limit=300&brand=5786&dest=-1257786&sort=pricedown" type Response struct { Data struct { Products []Product `json:"products"` } `json:"data"` } type Product struct { ID int `json:"id"` Name string `json:"name"` Price int `json:"priceU"` Rating float32 `json:"reviewRating"` Sale int `json:"sale"` New bool `json:"isNew"` } func main() { var allProducts []Product for i := 1; ; i++ { page, err := fetchPage(i) if err != nil { log.Fatal(err) // TODO } allProducts = append(allProducts, page...) if len(page) == 0 { break } } fmt.Println(allProducts) fmt.Println(len(allProducts)) } func fetchPage(i int) ([]Product, error) { resp, err := http.Get(fmt.Sprintf(URL, i)) if err != nil { return nil, err } defer resp.Body.Close() if resp.StatusCode != 200 { return nil, errors.New(resp.Status) } var response Response err = json.NewDecoder(resp.Body).Decode(&response) if err != nil { return nil, err } return response.Data.Products, nil }
The above is the detailed content of I have several JSONs with the same structure. Their objects are arrays of objects. How can I append these arrays into an array?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The article explains how to use the pprof tool for analyzing Go performance, including enabling profiling, collecting data, and identifying common bottlenecks like CPU and memory issues.Character count: 159

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

This article demonstrates creating mocks and stubs in Go for unit testing. It emphasizes using interfaces, provides examples of mock implementations, and discusses best practices like keeping mocks focused and using assertion libraries. The articl

OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

This article explores Go's custom type constraints for generics. It details how interfaces define minimum type requirements for generic functions, improving type safety and code reusability. The article also discusses limitations and best practices

The article discusses Go's reflect package, used for runtime manipulation of code, beneficial for serialization, generic programming, and more. It warns of performance costs like slower execution and higher memory use, advising judicious use and best

The article discusses using table-driven tests in Go, a method that uses a table of test cases to test functions with multiple inputs and outcomes. It highlights benefits like improved readability, reduced duplication, scalability, consistency, and a

This article explores using tracing tools to analyze Go application execution flow. It discusses manual and automatic instrumentation techniques, comparing tools like Jaeger, Zipkin, and OpenTelemetry, and highlighting effective data visualization
