fix: add missing typings for list context provider

[gab1618]

What problem is this solving?

It adds a missing property that the list context provider accepts, but is not declared on the typings.

I tried to use the ListContextProvider component in another Vtex React app, but I couldn't properly use it, due to the typings being incomplete:

In the end, I had to come up with this nasty solution that declares a wrapper and forces any typings into everything, which is far from ideal.

How to test it?

Just check if the typings are fine, since I didn't make any change other than the typings.

Screenshots or example usage:

I won't have any, since this is not a visual thing

Describe alternatives you've considered, if any.

Related to / Depends on

How does this PR make you feel? 🔗

🗿

![](put .gif link here - can be found under "advanced" on giphy)

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[vtex-io-docs-bot]

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

• There's nothing new to document 🤔
• I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

• I just updated 🎉🎉

[gab1618]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)
• Minor (backwards-compatible functionality)
• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞