gjson | Make it easy to read arbitrary JSON in Go | JSON Processing library

I am trying to remove feature_id property from properties array and move upwards.

I want to check whether an interface that comes from my application is valid json or not. I have searched. It could be duplicate of here: duplicate (but it did not work) I found some methods. One of them is Marshaling then Unmarshaling the interface like the following code:

I want to validate an openapi spec in a similar fashion as its done here : http://bigstickcarpet.com/swagger-parser/www/index.html but the difference is that Ill use GO to code the tool and its only a CLI.

I am trying to use this :

https://github.com/go-openapi/validate

But the main problem is that the documentation is almost non existent. I came here looking for help of someone that might previously used this library and can give me a MINIMAL example of sending a file containing a spec like such and having this library to throw all the errors or warnings in a similar fashion to the online Swagger validator.

I already can read a file and do some manual validation of the fields on it but of course thats not what I need to do and its just a sample.

Additionally, as a secondary question, I want to post this same question on their GitHub repo but I get this :

and I have no idea how to "review" these guidelines so I can post my question.

I have 3 data layers (in geoJSON) which I added to my map. I want certain features to only show at a higher zoom level. The way I am going about it right now is through the feature styling as so:

I am new to Go lang and trying to parse a JSON of following form and get all objects in records array.

I've been trying to extract some JSON by unmarshalling my json response into structs, but I have no idea why it's not doing it properly. I've also tried gjson but same result. Am I missing something here?

JSON Result:

I have consulted a lot of questions and I still can't find the solution to my problem.

I am doing an application and some of the classes have attributes of the geometry or point type, but when doing persistence tests, everything goes well until I try to save a point.

I want to add that I need to use this type of geometry (import org.locationtech.jts.geom.Point;) and all the solutions I find is with the type (import com.vividsolutions.jts.geom.Point;)

I think the problem is when it comes to serializer, I have one that should work fine but a function gives me an error.

pom.xml

i want to update the markers on leaflet map without refreshing the page , say every 3 seconds. the code i have tried so far is as below:

I have a json document of a Kubernetes Pod, here's an example: https://github.com/itaysk/kubectl-neat/blob/master/test/fixtures/pod-1-raw.json

I'd like to traverse spec.containers[i].volumeMounts and delete those volumeMount objects where the .name starts with "default-token-". Note that both containers and volumeMounts are arrays.

Using jq it took me 1 min to write this 1 line: try del(.spec.containers[].volumeMounts[] | select(.name | startswith("default-token-"))). I'm trying to rewrite this in Go.

While looking for a good json library I settled on gjson/sjson. Since sjson doesn't support array accessors (the # syntax), and gjson doesn't support getting the path of result, I looked for workarounds.
I've tried using Result.Index do delete the the result from the byte slice directly, and succeeded, but for the query I wrote (spec.containers.#.volumeMounts.#(name%\"default-token-*\")|0) the Index is always 0 (I tried different variations of it, same result).
So currently I have some code 25 line code that uses gjson to get spec.containers.#.volumeMounts and iterate it's way through the structure and eventually use sjson.Delete to delete. It works, but it feels way more complicated then I expected it to be.

Is there a better way to do this in Go? I'm willing to switch json library if needed.

EDIT: I would prefer to avoid using a typed schema because I may need to perform this on different types, for some I don't have the full schema.
(also removed some distracting details about my current implemetation)