Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REQUEST] Implement component-specific attributes from v3 #480

Closed
1 task
FayeDel opened this issue Feb 7, 2022 · 1 comment
Closed
1 task

[REQUEST] Implement component-specific attributes from v3 #480

FayeDel opened this issue Feb 7, 2022 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@FayeDel
Copy link
Collaborator

FayeDel commented Feb 7, 2022

What is the feature you're proposing?
Essentially, some v3-based properties like ctx.component, ctx.selected_options, etc, are not present in v4. They can be iterated manually, but it would be nicer if there'd be a @property based attribute that has the lib abstract the iteration and such similar to how v3 was, so we can also have ctx.label (ctx.component could arguably be redundant if you're using a callback for one singular component, or not for multiple stacked decorator usage.)

Additional Information

  • My feature request is related to an existing Issue.
    • Issue (if referenceable):
@FayeDel FayeDel added documentation Improvements or additions to documentation enhancement New feature or request labels Feb 7, 2022
@Damego
Copy link
Member

Damego commented Feb 7, 2022

Ig ctx.component should be.
We can change component and then edit message with updated components

ctx.component.label/style/disabled = *something*
await ctx.edit(components=ctx.message.components)

@EdVraz EdVraz closed this as completed Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants