-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Remove validation dependency #25335
Remove validation dependency #25335
Conversation
/azp run java - spring - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
/azp run java - spring - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - spring - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - spring - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
…dency_gzh # Conflicts: # sdk/spring/spring-cloud-azure-starter-cosmos/pom.xml
throw new AADB2CConfigurationException("Sign in user flow key '" | ||
+ loginFlow + "' is not in 'user-flows' map."); | ||
} | ||
if (!isValidURL(logoutSuccessUrl)) { |
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.
This should move into validateURLProperties
?
if (!isValidURL(logoutSuccessUrl)) { | ||
throw new AADB2CConfigurationException("logout success should be valid URL."); | ||
} | ||
if (!isValidURL(baseUri)) { |
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.
In original logic, baseUri
can be empty, but now it can't.
*/ | ||
private void validateURLProperties() { | ||
if (!CollectionUtils.isEmpty(userFlows)) { | ||
if (!StringUtils.hasText(tenant) && !StringUtils.hasText(baseUri)) { |
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.
!StringUtils.hasText(tenant)
is not belong to validateURLProperties
. The method name will make the code confusing.
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.
updated
/azp run java - spring - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - spring - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
* @param uri | ||
* @return whether is uri is valid or not. | ||
*/ | ||
private boolean isValidURL(String uri) { |
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.
this should be a more common util, thus should be located in a util class in core , this properties class is not the proper place
.../main/java/com/azure/spring/cloud/autoconfigure/cosmos/properties/AzureCosmosProperties.java
Show resolved
Hide resolved
A PR should contains one thing, apperently this PR does alot more than what the title / description said |
/azp run java - spring - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
API changes have been detected in API changes + public enum ErrorOptions {
+ THROW,
+ NO_THROW;
+ }
+ public RequestOptions setErrorOptions(EnumSet<ErrorOptions> errorOptions) |
/azp run java - spring - tests |
/azp run java - spring - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
This PR is mainly about
spring-boot-starter-validation
to simplify module dependency.spring-cloud-azure-starter-data-cosmos