Download the PHP package andymswick/expo without Composer
On this page you can find all versions of the php package andymswick/expo. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download andymswick/expo
More information about andymswick/expo
Files in andymswick/expo
Package expo
Short Description Laravel notification driver for Expo Push Notifications.
License MIT
Homepage https://github.com/andymswick/expo
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package expo
Expo notification channel for Laravel
This package makes it easy to send push notifications to your Expo app with Laravel 5.5+ and 6.0.
For more information on how to set up push notifications from within your Expo app, please refer to their documentation on push notifications.
Contents
- Installation
- Usage
- Available Message methods
- Changelog
- Testing
- Security
- Contributing
- Credits
- License
Installation
You can install this package via composer using this command:
The package will automatically register itself.
You can publish the optional migration with:
After the migration has been published you can add the push_token the users table by running the migrations:
You can publish the optional config-file with:
This is the contents of the published config file:
Usage
If a notification supports being sent as a Expo push notification, you should define a toExpo method on the notification class. This method will receive a $notifiable entity and should return a NotificationChannels\Expo\ExpoMessage instance. Expo messages may contain a title and body as well as "jsonData" that adds additional data that is sent to the Expo app. Let's take a look at a basic toExpo example:
A to method is required if the notifiable does not have a token value set in config/expo.php. You can optionally publish this config as well as a migration that will add a push_token to the users table after remember_token.
Below is an example of using the to method, if you would rather not use the config or migration.
Available Message methods
to(string): Set the recipient of the message. This will default to the notifiable'spush_tokenattribute.title(string): Set the title of the message.body(string): Set the body of the message.enableSound(): Enable the default sound to be played.disableSound(): Disable the default sound to be played.badge(int): Set the badge to the int value. (iOS only)setTtl(int): Set the time to live value. (iOS only)setChanelId(int): Set the chanelId of the notification. (Android only)setJsonData(array|string): Set the extra data of the notification, can be passed an array or a json string.toArray(): Converts the message to an array.
Changelog
Please see CHANGELOG for more information what has changed recently.
Testing
Security
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
Contributing
Please see CONTRIBUTING for details.
Credits
- Andy Swick
- All Contributors
License
The MIT License (MIT). Please see License File for more information.
All versions of expo with dependencies
guzzlehttp/guzzle Version ^6.3
illuminate/notifications Version ~5.5 || ~6.0
illuminate/support Version ~5.5 || ~6.0