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

Security checks #694

Merged
merged 1 commit into from Jul 23, 2013
Merged

Security checks #694

merged 1 commit into from Jul 23, 2013

Conversation

@emanuele45
Copy link
Contributor

emanuele45 commented Jul 18, 2013

I was wondering if this it a good thing to do or it is better to keep everything in one place...dunno.

Based on a not yet merged branch so it brings with him some unrelated commits...

Signed-off-by: emanuele <emanuele45@gmail.com>
@norv

This comment has been minimized.

Copy link
Contributor

norv commented Jul 23, 2013

I presume you rebased it already (or the branch was merged) because it's fine now.

The split of the code is welcome. I don't see downsides of the move to layer... it's unexpected to use layers as non-overridable, but, it's those always-there checks. Thank you, lets move through the code with it. :)

norv added a commit that referenced this pull request Jul 23, 2013
@norv norv merged commit 48043db into elkarte:master Jul 23, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.