-
-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bring me a Feature! #61
Comments
Adding CORS feature and my package :) |
What about a package that does the testing automatically every time the code or the test changes? |
@veerajongit Sounds great! Would it be possible also to enable these tests for TravisCI? |
Would you guys want the ability to archive users similar to the idea of SoftDeletes? |
Hi @nowendwell - this might a good improvement here. Thanks! |
I think I can spin something up. Thinking a Trait (Forgetable or GDPRPolicy or something) that would call a variable on the model to find the relationships. The trait would have download() and permanentDelete() methods that do the respective tasks. I'm thinking protected $gdpr_relations = [
'providers',
'protectionValidation',
'protectionShopTokens'
]; That way you could call // Route
Route::delete('/user/{user}', 'UserController@permanentDelete');
// User Controller
public function permanentDelete(User $user)
{
$user->permanentDelete();
return back();
}
// GDPRPolicy Trait
public function permanentDelete()
{
foreach($this->gdpr_relations as $relation) {
$relation->forceDelete();
}
return true;
} As for the data provisioning (downloading data right?) do you want to pull in an Excel library and make it fancy or just stick with an fputcsv kinda thing? I'm thinking if we're just going the fputcsv route something like this
Let me know your thoughts. |
Hi @nowendwell the suggestion looks really good - let's do it. |
New feature request added - #73 Add Guided Tour |
Hacktoberfest feature challenge!
Suggest and Pull a new feature, which is adding great value for the Laravel Boilerplate users.
@ALL contributors
In the case of unique->tested->accepted feature we'll be happy to include your GitHub handle in the list of contributors on the main boilerplate page (README.md) - https://github.com/Labs64/laravel-boilerplate#contributors-and-supporters
The text was updated successfully, but these errors were encountered: