Skip to main content

📢 Reporting Issues

We appreciate you taking the time to report issues with the Laravel Like package. Your feedback helps us improve the package for everyone.

Before You Report

  1. Search Existing Issues

    • Check if the issue has already been reported on our GitHub Issues page.
    • Look at the closed issues as well, as your issue might have been resolved.
  2. Check the Documentation

    • Review the documentation to ensure you're using the package correctly.
    • Check the FAQ section below for common issues.

How to Report an Issue

  1. Create a New Issue

    • Go to New Issue
    • Select "Bug Report"
    • Fill in the template with as much detail as possible
  2. Required Information

    • Laravel version
    • Package version
    • PHP version
    • Steps to reproduce the issue
    • Expected behavior
    • Actual behavior
    • Any relevant error messages or logs

Writing a Good Bug Report

A good bug report includes:

  • Clear Title: Briefly describe the issue
  • Detailed Description: Explain what you're trying to do
  • Reproduction Steps: Step-by-step instructions to reproduce the issue
  • Code Examples: Relevant code snippets that demonstrate the issue
  • Error Messages: Include any error messages or stack traces
  • Screenshots: If applicable, add screenshots to help explain the problem

Issue Triage Process

  1. Initial Review: A maintainer will review your issue
  2. Needs More Info: If more information is needed, we'll ask for it
  3. Reproduction: We'll try to reproduce the issue
  4. Prioritization: The issue will be prioritized based on severity and impact
  5. Resolution: The issue will be fixed in an upcoming release

Frequently Asked Questions

Why was my issue closed?

Issues might be closed if:

  • They are duplicates of existing issues
  • They don't follow the issue template
  • They lack sufficient information to reproduce
  • They are not related to the package

How can I speed up the resolution of my issue?

  • Provide a clear, minimal reproduction
  • Be responsive to requests for more information
  • If possible, submit a pull request with a fix

Security Issues

If you discover a security vulnerability within Laravel Like, please email [email protected] instead of using the issue tracker. All security vulnerabilities will be promptly addressed.