-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[SHIRO-805] Spelling #269
[SHIRO-805] Spelling #269
Conversation
Thanks! Btw, some classes get renamed. If they are not in a test folder, we'd need to let them misspelled the way they are. |
web/src/main/java/org/apache/shiro/web/filter/mgt/PathMatchingFilterChainResolver.java
Outdated
Show resolved
Hide resolved
This is now roughly:
The commits I've dropped are variable/function/class renames. Note for simplicity, if a code rename includes a comment change, that was included. |
@jsoref can you squash the commits please? |
(This is just a rebased version before squashing.) |
e2f648b
to
dcb9e4b
Compare
@fpapon ? |
Maybe just #269 (comment) left, then we are good imho. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some nits
core/src/main/java/org/apache/shiro/authc/pam/ModularRealmAuthenticator.java
Outdated
Show resolved
Hide resolved
* authentication state that might exist, thereby effectively "unauthenticating" the {@code Subject}. | ||
* authentication state that might exist, thereby effectively removing the "authenticated" state of the {@code Subject}. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not 100% sure about this one. I know "to unauthenticate" is not a common word, but it is easier to understand than "removing the >authenticated<-state".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unauthenticate really isn't a word. Conceptually the word would be deauthenticate (but even that isn't in Google Chrome's dictionary -- nor is it in the dictionary I'm using, although I'd be ok w/ it).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe @bdemers can think of something else?
core/src/test/java/org/apache/shiro/realm/jdbc/JDBCRealmTest.java
Outdated
Show resolved
Hide resolved
core/src/test/java/org/apache/shiro/realm/jdbc/JDBCRealmTest.java
Outdated
Show resolved
Hide resolved
core/src/test/java/org/apache/shiro/realm/jdbc/JDBCRealmTest.java
Outdated
Show resolved
Hide resolved
core/src/test/java/org/apache/shiro/realm/jdbc/JDBCRealmTest.java
Outdated
Show resolved
Hide resolved
core/src/test/java/org/apache/shiro/realm/jdbc/JDBCRealmTest.java
Outdated
Show resolved
Hide resolved
Fwiw, I'm trying to update this PR, I have everything resolved, but there's quite a bit of additional drift between when I started and now... So, I'm also trying to get my tool to give new happier output. |
Sorry it took us so long. Shouldn't happen again! :) |
* account * against * and * application * authentication * authorization * authorizer * automatically * axes * both * build * case * consistent * contains * control * controls * created * deauthenticating * defaults * defined * delimited * delimiter * deserialized * deserializes * e.g. * efficient * encapsulate * encryption * environment * et al. * etc. * evaluate * evaluator * exception * explicitly * false * filters * from * hash format * hashed * hierarchy * i.e. * identifier * identifying * immediately * implementation * implementers * inferring * injectable * iterator * join point * manner * modifier * nonexistent * obtained * overridden * password * performing * permission * permissions * preemptively * recognized * reget * remnant * request * required * resolvable * returned * safely * session * subsequent * successfully * type * undertow * usually * wield Signed-off-by: Josh Soref <[email protected]>
@@ -159,8 +159,8 @@ protected AuthorizationInfo buildAuthorizationInfo(Set<String> roleNames) { | |||
Set<String> roleNames; | |||
roleNames = new LinkedHashSet<String>(); | |||
|
|||
SearchControls searchCtls = new SearchControls(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not strictly necessary, but ok for me.
@jsoref thanks for your contribution! |
view it on GitHub
…------------------ 原始邮件 ------------------
发件人: "apache/shiro" ***@***.***>;
发送时间: 2021年8月4日(星期三) 晚上6:13
***@***.***>;
***@***.***>;
主题: Re: [apache/shiro] [SHIRO-805] Spelling (#269)
@jsoref thanks for your contribution!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at jsoref@c0e3b03#commitcomment-45334058
The action reports that the changes in this PR would make it happy: jsoref@276884c
Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.
Following this checklist to help us incorporate your contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
[SHIRO-XXX] - Fixes bug in SessionManager
,where you replace
SHIRO-XXX
with the appropriate JIRA issue. Best practiceis to use the JIRA issue title in the pull request title and in the first line of the commit message.
mvn clean install apache-rat:check
to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.git rebase -i
.Trivial changes like typos do not require a JIRA issue (javadoc, comments...).
In this case, just format the pull request title like
(DOC) - Add javadoc in SessionManager
.If this is your first contribution, you have to read the Contribution Guidelines
If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement
if you are unsure please ask on the developers list.
To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I expect to squash this PR near the end. But it's much easier for me to address review comments before squashing rather than after, as they generally address individual word families.
If there are files that you don't want changed, please let me know -- dropping them is fairly easy.