Skip to content
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

Fix unintended relation to users when a model uses HasPermissions trait #95

Conversation

brandonlim-hs
Copy link

Description

Moved users method from HasPermissions trait to Role model. The list of users related to Role or Permission are still accessible from the respective models. For example, $role->users and $permission->users

Motivation and context

Models that use HasPermissions trait should not unintentionally be related to User model. fixes #94

How has this been tested?

Added additional tests to assert that a model that uses HasRoles or HasPermissions trait does not have users method

/** @test */
public function a_model_that_uses_hasPermissions_trait_should_not_have_users_method()
{
    $this->assertFalse(method_exists($this->testUser, 'users'));
}
/** @test */
public function a_model_that_uses_hasRoles_trait_should_not_have_users_method()
{
    $this->assertFalse(method_exists($this->testUser, 'users'));
}

Screenshots (if appropriate)

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

Go over all the following points, and put an x in all the boxes that apply.

Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.

  • I have read the CONTRIBUTING document.
  • My pull request addresses exactly one patch/feature.
  • I have created a branch for this patch/feature.
  • Each individual commit in the pull request is meaningful.
  • I have added tests to cover my changes.
  • If my change requires a change to the documentation, I have updated it accordingly.

If you're unsure about any of these, don't hesitate to ask. We're here to help!

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling cc21354 on brandonlim-hs:bugfix-unintended-users-relation into 954633b on mostafamaklad:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling cc21354 on brandonlim-hs:bugfix-unintended-users-relation into 954633b on mostafamaklad:master.

@mostafamaklad mostafamaklad merged commit b3bd147 into mostafamaklad:master May 11, 2019
mostafamaklad added a commit that referenced this pull request Feb 24, 2020
…ation

Fix unintended relation to users when a model uses HasPermissions trait
sloan58 referenced this pull request in sloan58/laravel-permission-mongodb Feb 7, 2024
…ation

Fix unintended relation to users when a model uses HasPermissions trait
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unintended relation to users when a model uses HasPermissions trait
3 participants