diff --git a/.github/workflows/alert.yml b/.github/workflows/alert.yml
index a5f2bc58..7667504b 100644
--- a/.github/workflows/alert.yml
+++ b/.github/workflows/alert.yml
@@ -1,35 +1,39 @@
-name: Laravel
+name: Testing
on:
push:
- branches: [ "master" ]
+ branches: [ "master", "feature/laravel-10" ]
pull_request:
branches: [ "master" ]
+permissions:
+ contents: read
+
jobs:
- laravel-tests:
+ build:
runs-on: ubuntu-latest
steps:
- - uses: shivammathur/setup-php@15c43e89cdef867065b0213be354c2841860869e
- with:
- php-version: '8.0'
- uses: actions/checkout@v3
- - name: Copy .env
- run: php -r "file_exists('.env') || copy('.env.example', '.env');"
- - name: Install Dependencies
- run: composer install -q --no-ansi --no-interaction --no-scripts --no-progress --prefer-dist
- - name: Generate key
- run: php artisan key:generate
- - name: Directory Permissions
- run: chmod -R 777 storage bootstrap/cache
- - name: Create Database
- run: |
- mkdir -p database
- touch database/database.sqlite
- - name: Execute tests (Unit and Feature tests) via PHPUnit
+
+ - name: Validate composer.json and composer.lock
+ run: composer validate --strict
+
+ - name: Cache Composer packages
+ id: composer-cache
+ uses: actions/cache@v3
+ with:
+ path: vendor
+ key: ${{ runner.os }}-php-${{ hashFiles('**/composer.lock') }}
+ restore-keys: |
+ ${{ runner.os }}-php-
+
+ - name: Install dependencies
+ run: composer install --prefer-dist --no-progress
+
+ - name: Execute tests
env:
DB_CONNECTION: sqlite
DB_DATABASE: database/database.sqlite
- run: vendor/bin/phpunit
+ run: php vendor/bin/testbench package:test
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 00000000..18c91471
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+ and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+ overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+ advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+ address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.
diff --git a/README.md b/README.md
index a878083b..c649f1dd 100644
--- a/README.md
+++ b/README.md
@@ -1,206 +1,126 @@
-# Alert
+
+
+
-[](https://gitter.im/digitlimit/alert?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+> Version 2.0
-Alert is designed to make flashing messages in Laravel Applications a breeze.
-Tested and works in Laravel 5 or less
+Alert is Laravel package for displaying different types of messages in Laravel application views.
+It's designed to make flashing messages in Laravel Applications a breeze, with a lot of easy to use and fluent methods.
-### For this to work you need to include Twitter Bootstrap in your page
+## Quick Start
-## Installation
+1. Install Alert with composer:
-Add alert in your composer.json file:
-
-```php
-"require": {
- "digitlimit/alert": "v1.0"
-}
```
-
-Then run
-```command
-composer update
+composer require digitlimit/alert
```
-In Laravel 5 include Alert Service Provider within config/app.php or app/config/app.php in Laravel 4
+2. Somewhere in the blade template
-```php
-'providers' => [
- 'Digitlimit\Alert\AlertServiceProvider'
-];
+```
+
```
-You can also include alert facade in aliases array in same file above i.e config/app.php or app/config/app.php in Laravel 4
+Example:
-```php
-'aliases' => [
- 'Alert' => 'Digitlimit\Alert\Facades\Alert'
-];
```
+@extends('layouts.default')
+
+@section('content')
+
+
+
+
+
+
-## Usage
+
+ @include('form.profile')
+
+
-In your controller simply set your alert before redirection like so:
+ @include('partials.footer')
+@endsection
+```
-In laravel 5 controller for example:
+NB: At the moment the alert components are built with Twitter Bootstrap 5, and can be customized to use other CSS classes.
+Need to ensure bootstrap is included on the page.
-```php
-success()
- ->closable();
-
- return redirect()->route('users.getRegister');
- }
-}
+namespace App\Http\Controllers;
+use Alert;
-class LoginController extends Controller
+class DashboardController extends Controller
{
- public function postLogin(Request $request)
+ public function index()
{
- /*run validation on request parameters*/
- $validator = validator($request->only(['email','password']), [
- 'email' => 'required|email',
- 'password' => 'required|string',
- ]);
-
- /*return errors to view if any*/
- if($validator->fails()){
-
- Alert::form('Some errors occured','Opps')
- ->error();
-
- return redirect()
- ->back()
- ->withErrors($validator);
- }
+ Alert::message('Welcome! Please complete your profile')
+ ->info()
+ ->flash();
+
+ return view('home');
}
}
```
-Then in your view your can include the flash message to your view like so:
-
-```html
-
-
- @include('alert::form')
-
-
-
-```
-##### Form Alert Example
-
-
-
-## Features
-There are basically three types of alert messages you can flash
-
-#### Form - used mostly to display message in the header of your form
-
-Some where in the controller:
-```pph
-//This simply displays a success message
-Alert::form('Your account was successfully created','Congratulations')->success();
-```
-Some where in the view:
-```html
-@include('alert::form')
-```
+4. Result
-#### Notify - used mostly on the header of your page
+
-Some where in the controller:
-```pph
-//This simply displays a success message
-Alert::notify('Your account is going to expire today.','Info')->info();
-```
-Some where in the view layout where you want the alert to appear:
-```html
-@include('alert::notify')
-```
-#### Modal - used mostly to display an overlay message
+## Documentation
-Some where in the controller:
-```php
-//This simply displays a success message
-Alert::modal('Thanks for joining us.','Title')->info();
-```
-Some where in the view layout:
-```html
-@include('alert::modal')
-```
+Learn how to get started with Alert and then dive deeper into other and advanced topics:
-#### Customize alert views
-To customized various alert views run artisan command below
-```
- php artisan vendor:publish --provider="Digitlimit\Alert\AlertServiceProvider"
-```
+[Complete documentation](https://github.com/digitlimit/alert/wiki)
-This will publish `form.blade.php`, `modal.blade.php`, `notify.blade.php` and `sticky.blade.php`
-to publish views to `resources/views/vendor/alert` directory.
+## Change log
-The following helpers can be used in blade templates
+Coming soon
-**Alert Icon**
-This displays alert icon class e.g fa fa-cog
-Example:
-``
+## Code of conduct
-**Alert Status**
-This displays alert status
-Example:
-`
`
+We will behave ourselves if you behave yourselves. For more details see our
+[CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
-**Alert Title**
-This displays alert title
-Example:
-`
`
+Please read through our [contributing guidelines](./CONTRIBUTING.md). Included
+are directions for opening issues.
-**Form alert customization example**
+## Versioning
-```
-@if(Alert::has('form'))
-
+`..`
- @if(Alert::icon())@endif
+For more information on SemVer, please visit https://semver.org.
- @if(Alert::title()){{Alert::title()}}@endif {{Alert::message()}}
+* Any release may update the design, look-and-feel, or branding of an existing
+ icon
+* We will never intentionally release a `patch` version update that breaks
+ backward compatibility
+* A `minor` release **may include backward-incompatible changes** but we will
+ write clear upgrading instructions in UPGRADING.md
+* A `minor` or `patch` release will never remove icons
+* Bug fixes will be addressed as `patch` releases unless they include backward
+ incompatibility then they will be `minor` releases
-
-