Wappler Stripe Components & Outdated Data Structures

I'm finding more built-in Stripe components are not populating their data structures in my API's. This time, it's the simple Retrieve Customer component in Wappler not populating the customer's email address. Wappler's object model differs greatly from Stripe's API reference documentation.

Wappler's model, which is sorted alphabetically in the GUI, looks like this:

Stripe's current object model looks like this:

The question here isn't about fixing it. More apropos, the question is if Wappler's team plans to continue trying to support Stripe in this way going forward? Staying on top of Stripe's version changes is a challenge, understandably. There's no way using the built-in Stripe components to specify a version and therefore a data model. This has been raised in the past in the forums.

Wappler team: what is your position about how Stripe is going to be supported or not supported with built-in components going forward? Especially with version 7 and beyond?