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

[email protected] Planning and Task Tracking #220

Open
11 tasks
ThePhar opened this issue Nov 21, 2024 · 0 comments
Open
11 tasks

[email protected] Planning and Task Tracking #220

ThePhar opened this issue Nov 21, 2024 · 0 comments
Labels
is: documentation Improvements or additions to documentation is: enhancement New feature or request
Milestone

Comments

@ThePhar
Copy link
Owner

ThePhar commented Nov 21, 2024

Creating an issue for tracking planned features, deprecated apis, etc for version 2.1 of the library.

The goal is to maintain backwards compatibility for clients that have moved to 2.0 for the time being, while improving the interface and capabilities for new or future users. Anything marked as deprecated will not be removed until a 3.0 release.

  • Add client option to return all arguments for any event as an object, instead of positional parameters.
    • Requires opting in on the Client object, otherwise returns the positional arguments instead of an object.
    • A deprecation warning to be displayed that the positional parameters version will be removed in version 3.0, where it will become the default.
  • On the MessageEvents.message event, include a property with the event type, for easy filtering without setting up event listeners for all other message types.
  • Create a "ready" system for all managers after initial connection to before Client.login resolves, especially for cases where data needs to be fetched from storage.
    • Deprecate ItemEvents.hintsInitialized after this, since it should use the ready system and thus will never be needed as the client won't resolve until all hints are loaded (to be removed in 3.0.0).
  • Add events for the following scenarios:
    • A player's status changed.
  • Expose the underlying network item object on Item as needed.
  • Ensure all items, players, and hints pass equality checks.
  • Add support for extending client capabilities via user-defined manager objects.
    • Create an example with the Gifting Specification and create npm package.
    • Add known extensions to documentation.

More potentially to come.

@ThePhar ThePhar added is: documentation Improvements or additions to documentation is: enhancement New feature or request labels Nov 21, 2024
@ThePhar ThePhar added this to the 2.1 Release milestone Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is: documentation Improvements or additions to documentation is: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant