Future plans for Modals and Input Text

[krittick]

Summary

This meta issue outlines future plans to improve our implementation of modals and input text components

Enhancements planned:

Modal

• timeout feature (not possible until discord adds support for dismissing the modal without submitting it)
• stop() method
• decorator
• wait() method (Add wait() method to Modal class #1013)
• on_error event
• ApplicationContext shortcut methods for sending modals
• better _ModalWeights class (currently just uses the same logic from _ViewWeights)
• better dispatching (look into removing ModalStore as a requirement)
• look into solving for ApplicationContext.respond behaves differently depending on situations (Slash command vs Modal dialog callback) #994
• more?

InputText

• decouple from Item inheritance
• enforce label length limits to avoid sending invalid requests to the API (in progress as part of Add library-level enforcement of component field limits #1065, more testing needed)
• add library-side enforcement of other limits on things like max_length etc (in progress as part of Add library-level enforcement of component field limits #1065, more testing needed)
• fix typing issues (e.g. label) (in progress)
• more?

Rejected proposals:

• Look at potentially moving away from Bot UI Kit (i.e. View-based approach) and treat them as higher level objects (may come as part of a larger rework to how other components are handled by the library) Not in line with library goals at this time.

Note: This issue is for organizational tracking purposes only. For discussion on any specific item, please reach out in our discord server.

[onerandomusername]

How were these issues not already fixed in any of the following pulls?
#993
#992
#988
#984
#969
#966
#630 -- initial implementation

[ooliver1]

That's a lot of PRs just for one feature tbh

[krittick]

It's a brand new feature that is evolving as users identify new use cases the original implementation didn't have. Most of these are new functionality additions as well, so weren't prioritized in previous PRs.

[krittick]

Closing as stale, new plans need realignment with our release schedule.