Update v3 branch

.github/dependabot.yml

@@ -0,0 +1,7 @@
+version: 2
+updates:
+- package-ecosystem: composer
+  directory: "/"
+  schedule:
+    interval: monthly
+  open-pull-requests-limit: 10

.github/pull_request_template.md

@@ -0,0 +1,27 @@
+## WHY
+
+### BEFORE - What was wrong? What was happening before this PR?
+
+??
+
+### AFTER - What is happening after this PR?
+
+??
+
+
+## HOW
+
+### How did you achieve that, in technical terms?
+
+??
+
+
+
+### Is it a breaking change or non-breaking change?
+
+??
+
+
+### How can we test the before & after?
+
+??

.github/release-drafter.yml

@@ -0,0 +1,42 @@
+name: Release Drafter
+
+on:
+  push:
+    # branches to consider in the event; optional, defaults to all
+    branches:
+      - master
+
+jobs:
+  update_release_draft:
+    runs-on: ubuntu-latest
+    steps:
+      # Drafts your next Release notes as Pull Requests are merged into "master"
+      - uses: release-drafter/release-drafter@v5
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+name-template: 'v$NEXT_PATCH_VERSION 🌈'
+tag-template: 'v$NEXT_PATCH_VERSION'
+categories:
+  - title: '🚀 Features'
+    labels:
+      - 'feature'
+      - 'enhancement'
+      - 'added'
+  - title: '🐛 Bug Fixes'
+    labels:
+      - 'fix'
+      - 'bugfix'
+      - 'bug'
+      - 'fixed'
+  - title: '⚙️ Changes'
+    labels:
+      - 'changed'
+      - 'dependencies'
+  - title: '🧰 Removed'
+    label: 'removed'
+change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
+template: |
+  ## Changes
+
+  $CHANGES

.github/stale.yml

@@ -4,7 +4,7 @@
 # https://probot.github.io/apps/stale/
 
 # Number of days of inactivity before an issue becomes stale
-daysUntilStale: 60
+daysUntilStale: 120
 # Number of days of inactivity before a stale issue is closed
 daysUntilClose: 14
 # Issues with these labels will never be considered stale

.github/support.yml

@@ -16,7 +16,7 @@ supportComment: >
 
   Here are all the Backpack communication mediums:
    - Long questions (_I have done X and Y and it won't do Z wtf_) - [Stackoverflow](https://stackoverflow.com/questions/tagged/backpack-for-laravel), using the ```backpack-for-laravel``` tag; this is recommended for most questions, since other developers can then find the answer on a simple Google search; also, people get points for answering - and who doesn't like StackOverflow points?!
-   - Quick help (_How do I do X_) - [Gitter Chatroom](gitter.im/BackpackForLaravel/Lobby);
+   - Quick help (_How do I do X_) - [Gitter Chatroom](https://gitter.im/BackpackForLaravel/Lobby);
    - Bug Reports, Feature Requests - Github Issues (here);
 
   Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or StackOverflow is thanks to our awesome _awesome_ community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.

.github/workflows/add-to-project.yml

@@ -0,0 +1,20 @@
+name: Add new bugs & PRs to This Week project
+
+on:
+  issues:
+    types:
+      - opened
+      - transferred
+  pull_request:
+    types:
+      - opened
+
+jobs:
+  add-to-project:
+    name: Add new bugs and PRs to This Week project
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/add-to-project@main
+        with:
+          project-url: https://github.com/orgs/Laravel-Backpack/projects/13
+          github-token: ${{ secrets.ADD_TO_PROJECT_PAT }}

.gitignore

@@ -0,0 +1,7 @@
+.idea/
+vendor/
+node_modules/
+.DS_Store
+.composer.lock
+composer.lock
+.phpunit.result.cache

.travis.yml

@@ -1,15 +1,16 @@
 language: php
 
 php:
-  - 7.0
-  - 7.1
   - 7.2
+  - 7.3
+  - 7.4
+  - 8.0
   - nightly
 
 matrix:
     allow_failures:
         - php: nightly
-        - php: 7.2
+        - php: 8.0
 
 sudo: false
 

CHANGELOG.md

@@ -2,36 +2,82 @@
 
 All Notable changes to `Backpack Generators` will be documented in this file
 
-## NEXT - YYYY-MM-DD
+------------
+IMPORTANT
+------------
+
+Starting with version 3, the changelog is kept inside the Releases tab in our this repo's Github page. Please check https://github.com/Laravel-Backpack/Generators/releases
+
+------------
+
+## 2.0.7 - 2020-03-05
+
+### Fixed
+- Upgraded PHPUnit;
+
+
+## 2.0.6 - 2020-01-06
+
+### Fixed
+- CrudController typehint;
+
+
+## 2.0.5 - 2019-11-11
+
+### Fixed
+- when generating CRUDs, route name should only have lowercase letters;
+
+
+## 2.0.4 - 2019-09-28
+
+### Fixed
+- removed applyConfigurationFromSettings() call from operation stub, since it's now being called automatically by CrudController, before it reaches that method;
+
+
+## 2.0.3 - 2019-09-28
+
+### Fixed
+- fixed crud command had Class 'Str' not found error in CrudBackpackCommand:53;
+- models are now generated with ```$guarded``` instead of ```$fillable``` by default, since the CRUDs now only save what fields have been added by CRUD, not everything that's inside the Request; this should speed up CRUD generation A LOT, by not having to edit the model before you edit the CRUD; it's an opinionated way to do things though - some people prefer $fillable, others $guarded; both work; it's just the default that has changed;
+
+
+## 2.0.2 - 2019-09-17
 
 ### Added
-- Nothing
+- command to generate a CRUD operation; ex: ```php artisan backpack:crud-operation Moderate```
 
-### Deprecated
-- Nothing
+
+## 2.0.1 - 2019-09-12
 
 ### Fixed
-- Nothing
+- it's better for ```setupXxxOperation()``` methods to be ```protected```;
+
+
+## 2.0.0 - 2019-09-12
+
+### Added
+- Backpack v4 support;
+- ```php artisan backpack:crud``` now also generates route and sidebar item;
 
 ### Removed
-- Nothing
+- Backpack v3 support;
 
-### Security
-- Nothing
+
+------------
 
 ## 1.2.7 - 2019-02-27
 
-## Added
+### Added
 - Backpack\Base 1.1 compatibility;
 
 ## 1.2.6 - 2019-01-16
 
-## Added
+### Added
 - CrudPanel reference to CrudController stb, for IDE code completion;
 
 ## 1.2.5 - 2018-11-22
 
-## Added
+### Added
 - support for Backpack/Base 1.0.0
 
 ## 1.2.4 - 2018-08-27

LICENSE.md

@@ -1,21 +1,21 @@
-# The MIT License (MIT)
+MIT License
 
-Copyright (c) 2016 Cristian Tone <[email protected]>
+Copyright (c) 2022 Cristian Tabacitu
 
-> Permission is hereby granted, free of charge, to any person obtaining a copy
-> of this software and associated documentation files (the "Software"), to deal
-> in the Software without restriction, including without limitation the rights
-> to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-> copies of the Software, and to permit persons to whom the Software is
-> furnished to do so, subject to the following conditions:
->
-> The above copyright notice and this permission notice shall be included in
-> all copies or substantial portions of the Software.
->
-> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-> IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-> FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-> AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-> LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-> OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-> THE SOFTWARE.
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.