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

Tracking Issue for poise-in-serenity #313

Open
2 of 6 tasks
GnomedDev opened this issue Oct 22, 2024 · 0 comments
Open
2 of 6 tasks

Tracking Issue for poise-in-serenity #313

GnomedDev opened this issue Oct 22, 2024 · 0 comments
Labels

Comments

@GnomedDev
Copy link
Member

GnomedDev commented Oct 22, 2024

We are currently trying to merge poise into serenity, to replace the standard framework for 0.13+. This entails quite a bit of rework to make sure that the state of poise matches serenity. This is the issue to track that effort.

Goals

  • Remove as much of poise that is not a command framework as possible
  • Remove unmaintained code, or split it off
  • Remove as much magic as possible

Progress

  • Remove user data setup (done, serenity-next)
  • Remove autocomplete magic (done, next, Remove magic from autocomplete #312)
  • Audit and cleanup Command (allocations, etc)
  • Audit and cleanup FrameworkOptions
  • Remove autoref specialisation for command handling, just use traits like everyone else
  • Remove help command infrastructure, as this is not needed for current/next and should be split out into a separate crate fo a bit
@GnomedDev GnomedDev pinned this issue Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant