Handling Multiple resource views per mip per layer

[Pikachuxxxx]

problem

Cubemap and 2D array textures will need different image views and handling per face per mip and native views will get complicated

Thoughts dump

what If I have 2 of ImageResourceView
ex.
ImageResourceView m_NativeResourceView this will contain the UAV/SRV for the entire resource as intended
and another
ImageResourceView m_ResourceViews[RAZIX_MAX_TEXTURE_LAYERS][RAZIX_MAX_TEXTURE_MIPS] = {};
This is will always store the 2D image view per layer/mip, since such a image view is almost always just a 2D image? not sure If I want to generalize this...

I think if someone wants a image view for bunch of layers and mips, we can have explicit API for that?

hmm makes sense, right
yeah it'll probably search for 6 faces from that base index and cause issues hmmm

struct ImageResourceView
{
    VkImageView uav = VK_NULL_HANDLE;
    VkImageView srv = VK_NULL_HANDLE;
    VkImageView rtv = VK_NULL_HANDLE;    // for swapchain
    VkImageView dsv = VK_NULL_HANDLE;
}


ImageResourceView m_ResourceViews[RAZIX_MAX_TEXTURE_LAYERS][RAZIX_MAX_TEXTURE_MIPS] = {};

I'm using this setup to store my image views per face/per mip, now the issues is with a RWTextureCube, since HLSL doesn't have it I need to stores a Cubemap SRV, Texture2DArray UAV and a Texture2D UAV for each layer per mip, which is getting very non-intuitive, any suggestions on how to store image views in a better way?