:sparkles: API For interacting with Message Components
See original GitHub issueMostly opening this issue so I can get it in the todo list. I don’t have a very good idea of what the API would be but It will probably use Client.wait_for
/Client.loop_for
so keep those in mind.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Sparkle API — sparkle 1.0.0 documentation
Sparkle API ¶. The program can be divided into two parts: The GUI which interacts with the user to get inputs and presents...
Read more >Message Components - Javacord
Components are interactive elements like buttons or hidden elements like ... You can add them to a message and interact with users in...
Read more >Changes to message objects on the way to support WYSIWYG
Messages authored by users and sent to your app via APIs like Events API, chat.postMessage , and conversations.history will expand to more ...
Read more >rreboucas/sparkle-dx - GitHub
Example Lightning App with a set of Generic Responsive Lightning Components capable of loading and interacting with data from any Salesforce Object.
Read more >Intro to Vertex Pipelines - Google Codelabs
... Use pre-built components for interacting with Vertex AI services, provided through the google_cloud_pipeline_components library ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve been thinking about an API like this
It looks a little bloated but I thought about it and if people do one command per cog it will be super easy to read since the indentation is low. If someone really hates it they can manually do stuff with
Client.loop_for
anyway but that would suck lol.i forgor 💀 to close this