diskinfo | read disk information with NodeJS | Runtime Evironment library

The ioutil.ReadAll already provides you the data in the type byte[]. Therefore you can just call json.Unmarshal passing it as a parameter.

Since that SubPartitions flag is coupled with Partitions, one option is to remove the SubPartitions field, and add a method that computes this value :

Some vuetify components are more forgiving in what they expect from their props, but v-data-table is not the one: it expects its items property to be filled with a proper array from the beginning. But in your case, it starts undefined.

One possible approach to solve this is to provide an empty array (as a default value), then replace its value with response.

Are you using bootstrap? I see in your HTML you are linking to a bootstrap stylesheet.

If you are using bootstrap, you are not using the correct classes on your column div's.

You should do something like this:

Filter return a new one:

The problem is that you pass a null-pointer for the Ranges argument and zero for RangeCount.

For Ranges you're supposed to pass a pointer to the first element or an array of QUERY_CHANGES_VIRTUAL_DISK_RANGE elements, and the RangeCount should be initialized to the number of elements in that array.

When the QueryChangesVirtualDisk function returns it will have modified RangeCount to be the number of initialized elements in the Ranges array.

From the documentation you linked to, about the RangeCount argument:

On input, the value indicates the number of QUERY_CHANGES_VIRTUAL_DISK_RANGE structures that the array that the Ranges parameter points to can hold. On output, the value contains the number of QUERY_CHANGES_VIRTUAL_DISK_RANGE structures that the method placed in the array.

In short: The function doesn't create this array for you, you must do it before you call the function.

First, be careful with the Format cmdlets. They should only be used at the very end and not saved in a variable.

Your New-Object cmdlet also doesn't reference your $diskinfo variable. So $_.DeviceID would be undefined because nothing is passed down the pipeline.

Also the extra sub-expression operators are unnecessary $().

I personally like the [pscustomobject] type accelerator over using New-Object as it's more readable.