Skip to content

Access control #3339

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

Merged
merged 1 commit into from
Dec 26, 2013
Merged

Access control #3339

merged 1 commit into from
Dec 26, 2013

Conversation

romaricdrigon
Copy link
Contributor

Hi,

One more PR about simplifying Security doc: several paragraphs were redundant, such as "Securing a controller", "Access Control in a Controller"...
I factored all relative sections in a part called "Access Control", logically coming after "Users" and "Roles" parts.

Q A
Doc fix? yes
New docs? no
Applies to 2.3+
Fixed tickets none

@romaricdrigon
Copy link
Contributor Author

On a relative topic, in 2.4 doc, you may want to add a reference to SensioFrameworkExtraBundle in AccessControl docs next to JMSSecurityExtra.

I'm waiting for this PR to be merged before submitting it.

Access Control
--------------

Now that you have Users, Roles, we can go further than URL patterns based authorization.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you should always avoid a form of "we" or "let's"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest Now that you have users and roles, [...]

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure to fully get your comments.
Does this phrasing sounds good to you? I kept capital letters as they are precise concepts.

Now that you have Users and Roles, you can go further than URL patterns based authorization.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed :)

@wouterj
Copy link
Member

wouterj commented Dec 14, 2013

👍 great job!

I reviewed all new lines, I'm not sure if I commented on things you changed, but it would be great if you could fix those too


In fact, anything in Symfony can be protected using a strategy similar to
the one seen in the previous section. For example, suppose you have a service
(i.e. a PHP class) whose job is to send emails from one user to another.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't it be which instead of whose?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's a job of the service, so it should be "whose" imo, but let's wait what our native thinks :)

@romaricdrigon
Copy link
Contributor Author

Hi,

@wouterj actually I didn't modified any content, but improving the existing document is always great :)
So I'll try some time to review & fix accordingly to your comments tonight.

@wouterj
Copy link
Member

wouterj commented Dec 17, 2013

👍 Thank you!

(btw, if you know how to do it: could you please squash your commits?)

@romaricdrigon
Copy link
Contributor Author

@wouterj this is done!

@weaverryan weaverryan merged commit 808d055 into symfony:2.3 Dec 26, 2013
@weaverryan
Copy link
Member

Great job Romaric! These are exactly the types of changes that I think are important, but can only be done if someone knowledgable has time to read through an entire chapter and think about how the information is being communicated. So, we really appreciate this!

Thanks!

@romaricdrigon
Copy link
Contributor Author

Thanks @weaverryan :)
At the moment I'm under a lot of work, later in January I should be able to continue working on the doc. Symfony doc was great, with your work soon it'll be ever more awesome!

@romaricdrigon romaricdrigon deleted the access-control branch December 26, 2013 17:43
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.

4 participants