mirror of
https://github.com/spring-projects/spring-boot.git
synced 2024-08-29 03:06:45 +08:00
Polish
This commit is contained in:
parent
7ff2cb5dc8
commit
73c65286ea
@ -8,7 +8,7 @@ $ fly -t spring set-pipeline -p spring-boot -c ci/pipeline.yml -l ci/parameters.
|
||||
----
|
||||
|
||||
NOTE: This assumes that you have credhub integration configured with the appropriate
|
||||
secrets
|
||||
secrets.
|
||||
|
||||
=== Release
|
||||
|
||||
|
@ -46,7 +46,7 @@ include::{snippets}loggers/single/http-response.adoc[]
|
||||
|
||||
|
||||
|
||||
[[loggerse-single-response-structure]]
|
||||
[[loggers-single-response-structure]]
|
||||
=== Response Structure
|
||||
|
||||
The response contains details of the requested logger. The following table describes the
|
||||
|
@ -19,7 +19,7 @@ include::{snippets}shutdown/http-response.adoc[]
|
||||
|
||||
|
||||
|
||||
[[shutdowm-shutting-down-response-structure]]
|
||||
[[shutdown-shutting-down-response-structure]]
|
||||
=== Response Structure
|
||||
|
||||
The response contains details of the result of the shutdown request. The following table
|
||||
|
@ -75,7 +75,7 @@ public class ReactiveSecurityAutoConfigurationTests {
|
||||
}
|
||||
|
||||
@Test
|
||||
public void doesNotConfigureDefaultUserIfUserDetailsRepositoryAvailable() {
|
||||
public void doesNotConfigureDefaultUserIfUserDetailsServiceAvailable() {
|
||||
this.contextRunner.withUserConfiguration(UserConfig.class, TestConfig.class)
|
||||
.withConfiguration(
|
||||
AutoConfigurations.of(ReactiveSecurityAutoConfiguration.class))
|
||||
|
@ -6686,7 +6686,7 @@ It then becomes important not to litter the application's main class with config
|
||||
settings that are specific to a particular area of its functionality.
|
||||
|
||||
Assume that you are using Spring Batch and you rely on the auto-configuration for it.
|
||||
Your could define your `@SpringBootApplication` as follows:
|
||||
You could define your `@SpringBootApplication` as follows:
|
||||
|
||||
[source,java,indent=0]
|
||||
----
|
||||
@ -6708,7 +6708,7 @@ at the same level as your application, as shown in the following example:
|
||||
----
|
||||
|
||||
NOTE: Depending on the complexity of your application, you may either have a single
|
||||
`ApplicationConfiguration` class for your customizations or one class per domain area when
|
||||
`@Configuration` class for your customizations or one class per domain area when
|
||||
it makes sense. The latter approach lets you enable it in one of your tests, if necessary,
|
||||
with the `@Import` annotation.
|
||||
|
||||
|
@ -362,7 +362,7 @@ public class CollectionBinderTests {
|
||||
Bindable<BeanWithNestedCollection> target = Bindable
|
||||
.of(BeanWithNestedCollection.class);
|
||||
BeanWithNestedCollection foo = this.binder.bind("foo", target).get();
|
||||
assertThat(foo.getValue()).isNotNull();
|
||||
assertThat(foo.getValue()).isEqualTo("one");
|
||||
assertThat(foo.getFoos().get(0).getValue()).isEqualTo("two");
|
||||
assertThat(foo.getFoos().get(1).getValue()).isEqualTo("three");
|
||||
}
|
||||
|
@ -41,7 +41,7 @@ public class SampleSecureWebFluxApplication {
|
||||
}
|
||||
|
||||
@Bean
|
||||
public ReactiveUserDetailsService userDetailsRepository() {
|
||||
public ReactiveUserDetailsService userDetailsService() {
|
||||
return new MapReactiveUserDetailsService(User.withDefaultPasswordEncoder()
|
||||
.username("foo").password("password").roles("USER").build());
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user