@pgamerx/djs-addon

@pgamerx/djs-addon

@pgamerx/djs-addon is a npm package that allows you to easily add fun features using DiscordJS

Basic information

Features

• Easy to use
• Supports interactions in many functions
• Works with Any Djs Version above 13
• Unique functions like Chatbot, ytSearch, Canvas, Reddit and much more!

Getting started

• Check out the complete guide at This Page

Support/Updates

• Feel free to join our Discord server for updates, any kind of support

Important Links

• Documentation - Documentation is available at This link

• Support - You can get support in our Discord Server

• Donate - Like what I do? Feel free to Donate me

Contributing to @pgamerx/djs-addon

We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:

• Reporting a bug
• Discussing the current state of the code
• Submitting a fix
• Proposing new features
• Becoming a maintainer

We Develop with Github

We use github to host code, to track issues and feature requests, as well as accept pull requests.

We Use Github Flow, So All Code Changes Happen Through Pull Requests

Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:

1. Fork the repo and create your branch from master.
2. If you've added code that should be tested, add tests.
3. Ensure the test suite passes.
4. Make sure your code lints.
5. Issue that pull request!

Any contributions you make will be under the MIT Software License

In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.

Report bugs using Github's issues

We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!

Write bug reports with detail, background, and sample code

This is an example of a bug report I wrote, and I think it's not a bad model. Here's another example from Craig Hockenberry, an app developer whom I greatly respect.

Great Bug Reports tend to have:

• A quick summary and/or background
• Steps to reproduce
  • Be specific!
  • Give sample code if you can. My stackoverflow question includes sample code that anyone with a base R setup can run to reproduce what I was seeing
• What you expected would happen
• What actually happens
• Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)

People love thorough bug reports. I'm not even kidding.