You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Introduction to Laravel Like projects. Get to know the Laravel Like projects. Learn about the Laravel Like projects. Configure and install Laravel Like into your Laravel projects.
4
-
keywords: ['laravel like', 'introduction', 'laravel like projects', 'laravel like introduction', 'configure laravel like', 'install laravel like']
5
-
tags: ['Introduction', 'Laravel Like', 'Configure', 'Configure laravel like', 'Install laravel like', 'Laravel Like Projects', 'Get Started', 'Laravel Like Introduction', 'Information', 'Laravel Like Information']
3
+
description: A comprehensive Laravel package for adding like, dislike, and love interactions to your Eloquent models with ease.
A powerful and flexible Laravel package that adds social interaction features to your Eloquent models with minimal setup.
17
17
18
-
A Laravel package to add **interaction functionality** to your Laravel models. It is a simple and easy-to-use package that allows you to add interaction functionality to your **Laravel models**.
18
+
19
19
20
-
<imgsrc="/images/laravel-like-thumb.webp"alt="CSlant Laravel Like Package"class="img-fluid" />
20
+
## ✨ Features
21
21
22
-
Some interactions provided by the package are: **Like, Dislike, Love**.
22
+
-**Multiple Interaction Types**: Support for likes, dislikes, and loves out of the box
-**Efficient Queries**: Optimized database queries for high performance
25
+
-**Polymorphic Relationships**: Works with any Eloquent model
26
+
-**Flexible Configuration**: Customize table names, model references, and more
27
+
-**Comprehensive API**: Simple, intuitive methods for all interaction types
28
+
-**Query Scopes**: Powerful filtering and sorting capabilities
29
+
-**UUID Support**: Optional UUID support for primary keys
30
+
-**Caching**: Built-in caching for better performance
31
+
-**Event-Driven**: Fires events for all interactions
23
32
24
-
The **CSLant Laravel Like** package is not limited to default interactions like "Like," "Dislike," or "Love." This package is designed with high flexibility, allowing you to easily add more types of reactions based on your needs.
33
+
## 🚀 Getting Started
25
34
26
-
You're not restricted to the built-in reactions | you can create and define any type of interaction you prefer.
35
+
### Requirements
27
36
28
-
Additionally, _you can customize the model names and behavior, so you're **not tied to the term "Like."**_
The package comes with sensible defaults, but you can customize its behavior by modifying the `config/like.php` file. Key configuration options include:
64
+
65
+
-`is_uuids`: Use UUIDs instead of auto-incrementing IDs
66
+
-`table_name`: Customize the interactions table name
67
+
-`interaction_model`: Specify a custom interaction model
68
+
-`users.model`: Configure the user model
69
+
-`users.foreign_key`: Set the user foreign key
35
70
36
-
## 📝 Information
71
+
## 📚 Documentation
37
72
38
-
-[Installation](getting-started/installation)
39
-
-[Configuration](getting-started/configuration)
73
+
Explore the comprehensive documentation to get the most out of Laravel Like:
74
+
75
+
-[Basic Usage](usage/liking_content.md) - Learn how to add interactions to your models
76
+
-[Checking Interactions](usage/check_if_interacted.md) - Determine if users have interacted with content
77
+
-[Counting Interactions](usage/counting_interactions.md) - Get interaction counts and statistics
78
+
-[Query Scopes](usage/query_scopes.md) - Filter and sort content by interaction data
79
+
-[Advanced Usage](usage/advanced_usage.md) - Custom interaction types and advanced features
80
+
81
+
## 🤝 Contributing
82
+
83
+
Contributions are welcome! Please see our [contributing guide](https://github.com/cslant/laravel-like/blob/main/CONTRIBUTING.md) for details.
84
+
85
+
## 📄 License
86
+
87
+
This package is open-sourced software licensed under the [MIT License](https://opensource.org/licenses/MIT).
description: Request new features for the Laravel Like projects. Request new features for the Laravel Like projects. Get the list of all feature requests available in the Laravel Like projects.
4
-
keywords: ['laravel like', 'feature requests', 'new features', 'request new features', 'feature requests for laravel like']
5
-
tags: ['Feature Requests', 'New features', 'Requests', 'Laravel Like Feature', 'Support']
3
+
description: Request new features for the Laravel Like package. Get the list of all feature requests available in the Laravel Like package.
4
+
keywords: ['laravel like', 'feature requests', 'new features', 'request new features', 'feature requests for Laravel Like']
If you have any feature requests, please open an issue with the `feature request` label on
16
-
the [GitHub repository](https://github.com/cslant/laravel-like/issues/new?assignees=&labels=&projects=&template=feature_request.md&title=).
15
+
We welcome and appreciate all feature requests from our community. Before submitting a new feature request, please check the existing [issues](https://github.com/cslant/laravel-like/issues) to see if it has already been requested.
16
+
17
+
## How to Request a Feature
18
+
19
+
1.**Check Existing Issues**
20
+
- Search the [GitHub issues](https://github.com/cslant/laravel-like/issues) to see if your feature has already been requested.
21
+
- Look at the [milestones](https://github.com/cslant/laravel-like/milestones) to see planned features.
22
+
23
+
2.**Create a New Issue**
24
+
- Go to [New Issue](https://github.com/cslant/laravel-like/issues/new/choose)
25
+
- Select "Feature Request"
26
+
- Fill in the template with as much detail as possible
27
+
28
+
## What Makes a Good Feature Request?
29
+
30
+
-**Clear Description**: Explain what you want to achieve and why it's valuable
31
+
-**Use Case**: Describe the problem you're trying to solve
32
+
-**Examples**: Provide code examples or mockups if applicable
33
+
-**Alternatives**: Mention any alternative solutions you've considered
34
+
35
+
## Feature Request Process
36
+
37
+
1.**Discussion**: The community and maintainers will discuss the feature
38
+
2.**Approval**: If accepted, it will be added to a milestone
39
+
3.**Implementation**: The feature will be developed and tested
40
+
4.**Release**: Included in the next release
41
+
42
+
## Currently Planned Features
43
+
44
+
Check our [project board](https://github.com/orgs/cslant/projects/2) to see what features are currently being worked on.
45
+
46
+
## Contributing
47
+
48
+
If you'd like to implement a feature yourself, please read our [Contributing Guide](https://github.com/cslant/laravel-like/blob/main/CONTRIBUTING.md) first.
description: Issues and bug reports for the Laravel Like projects. Report issues and bugs for the Laravel Like projects. Get the list of all issues available in the Laravel Like projects.
description: Issues and bug reports for the Laravel Like package. Report issues and bugs for the Laravel Like package. Get the list of all issues available in the Laravel Like package.
If you find yourself stuck using this package, found a bug, or have a feature request. Please open an issue on [GitHub](https://github.com/cslant/laravel-like/issues).
15
+
We appreciate you taking the time to report issues with the Laravel Like package. Your feedback helps us improve the package for everyone.
16
16
17
-
We appreciate detailed and accurate reports that help us identify and replicate the issue.
17
+
## Before You Report
18
+
19
+
1.**Search Existing Issues**
20
+
- Check if the issue has already been reported on our [GitHub Issues](https://github.com/cslant/laravel-like/issues) page.
21
+
- Look at the [closed issues](https://github.com/cslant/laravel-like/issues?q=is%3Aissue+is%3Aclosed) as well, as your issue might have been resolved.
22
+
23
+
2.**Check the Documentation**
24
+
- Review the [documentation](https://docs.cslant.com/laravel-like) to ensure you're using the package correctly.
25
+
- Check the [FAQ](#frequently-asked-questions) section below for common issues.
26
+
27
+
## How to Report an Issue
28
+
29
+
1.**Create a New Issue**
30
+
- Go to [New Issue](https://github.com/cslant/laravel-like/issues/new/choose)
31
+
- Select "Bug Report"
32
+
- Fill in the template with as much detail as possible
33
+
34
+
2.**Required Information**
35
+
- Laravel version
36
+
- Package version
37
+
- PHP version
38
+
- Steps to reproduce the issue
39
+
- Expected behavior
40
+
- Actual behavior
41
+
- Any relevant error messages or logs
42
+
43
+
## Writing a Good Bug Report
44
+
45
+
A good bug report includes:
46
+
47
+
-**Clear Title**: Briefly describe the issue
48
+
-**Detailed Description**: Explain what you're trying to do
49
+
-**Reproduction Steps**: Step-by-step instructions to reproduce the issue
50
+
-**Code Examples**: Relevant code snippets that demonstrate the issue
51
+
-**Error Messages**: Include any error messages or stack traces
52
+
-**Screenshots**: If applicable, add screenshots to help explain the problem
53
+
54
+
## Issue Triage Process
55
+
56
+
1.**Initial Review**: A maintainer will review your issue
57
+
2.**Needs More Info**: If more information is needed, we'll ask for it
58
+
3.**Reproduction**: We'll try to reproduce the issue
59
+
4.**Prioritization**: The issue will be prioritized based on severity and impact
60
+
5.**Resolution**: The issue will be fixed in an upcoming release
61
+
62
+
## Frequently Asked Questions
63
+
64
+
### Why was my issue closed?
65
+
66
+
Issues might be closed if:
67
+
- They are duplicates of existing issues
68
+
- They don't follow the issue template
69
+
- They lack sufficient information to reproduce
70
+
- They are not related to the package
71
+
72
+
### How can I speed up the resolution of my issue?
73
+
- Provide a clear, minimal reproduction
74
+
- Be responsive to requests for more information
75
+
- If possible, submit a pull request with a fix
76
+
77
+
## Security Issues
78
+
79
+
If you discover a security vulnerability within Laravel Like, please email [[email protected]](mailto:[email protected]) instead of using the issue tracker. All security vulnerabilities will be promptly addressed.
0 commit comments