mapstructure | Go library for decoding generic map values | JSON Processing library

You are rendering a component via an anonymous function on the component prop of a Route, this creates a new "instance" of Team each render.

Route render methods

When you use component (instead of render or children, below) the router uses React.createElement to create a new React element from the given component. That means if you provide an inline function to the component prop, you would create a new component every render. This results in the existing component unmounting and the new component mounting instead of just updating the existing component. When using an inline function for inline rendering, use the render or the children prop

Use the render prop to render the Team component and pass additional props.

The json parser in go does not differentiate between empty array and filled array. You can use Components instead of []interface{}, even if there is nothing in the json array, it will parse it just fine.

spf13/viper predominantly uses mapstructure package to convert between one native Go type to another i.e. when un-marshaling. You need to define an annotation that would cause any unused values to this map. There is an option to collect such reminder values. You need to modify the map to take an interface as

Use mapstructure tag instead of json:

Your problem trivially comes down to the fact, if the username field in your MyConfig struct is exported or not. It needs to uppercased to be "exported" for Unmarshal to decode the value into the struct.

playground - timeout running go build [...] Could I solve it❓

No. Sorry.

The Playground is a playground and not a build server or an application server.

So the problem lied with wrong imports.

Basically Deployments are defined in apps/v1beta2. What I was doing was importing "k8s.io/api/apps/v1beta1". I needed to change it to "k8s.io/api/apps/v1beta2"

Also for fetching that I needed to refer to clientset.AppsV1beta2() instead of clientset.ExtensionsV1beta1()

Instead of defer wg.Wait, use wg.Wait at the end of the for-loop. You are using the data constructed by the goroutines in the for-loop right after for-loop completes, and you're not waiting for all the goroutines to complete before you use that data.

When you use defer wg.Wait, waiting happens at the end of the function. The for-loop using the data operates on incomplete data because the goroutines are still running.

When you use wg.Wait at the end of the for-loop, you first wait for all the goroutines to end, and then use the data generated by them.

Use nested for loops: