Closed jacek-jablonski closed 3 years ago
Hi @jacek-jablonski , sorry for the delay in the response, we were not tracking properly the issues for this repo.
Thank you very much for reporting this bug.
You should not need to set the object modifier since the tool should be able to identify that is an object. I can see that for the other two elements of the object the empty string is properly identified.
We have some errors for arrays yet, I was able to reproduce the error and will try to fix it.
In the meanwhile, even it is not the real value and your metadata could be confusing you could set an array modifier to the full jobs
object, but it will show you that field in the README as []
.
Hi,
it seems like adding modifier to array item key breaks metadata validation. Here is minimal example:
Above works fine, but generates
undefined
forjobs[0].resources.limits
:So, lets annotate
jobs[0].resources.limits
with [object] modifier:This however breaks metadata validation:
Generally I am trying to document quite a big and complicated array element. Is it a recommended way to do it with
[0]
in parameter's path or is there more generic way? Thanks.