Skip to content

S
spring-framework

爱吃血肠 / spring-framework

通知 1
Star 0
Fork 0
S
spring-framework

前往新版Gitcode，体验更适合开发者的 AI 搜索 >>

切换分支/标签
  1. 22 3月, 2019 1 次提交
  3. 12 12月, 2018 1 次提交
  5. 22 11月, 2018 1 次提交
  7. 19 11月, 2018 2 次提交
  9. 08 8月, 2018 2 次提交
  11. 20 7月, 2018 1 次提交
  13. 01 7月, 2018 1 次提交
  15. 28 6月, 2018 3 次提交
  17. 09 3月, 2018 1 次提交
  19. 27 2月, 2018 1 次提交
  21. 25 2月, 2018 1 次提交
  23. 22 2月, 2018 1 次提交
  25. 11 2月, 2018 1 次提交
  27. 09 2月, 2018 2 次提交
  29. 06 2月, 2018 1 次提交
  31. 27 9月, 2017 1 次提交
  33. 15 9月, 2017 1 次提交
    • S
      Revisit nullability annotations · 1bc93e3d
      由 Sebastien Deleuze 提交于 
      This commit introduces the following changes.

1) It adds a new Spring @NonNull annotation which allows to apply
@NonNullApi semantic on a specific element, like @Nullable does.
Combined with @Nullable, it allows partial null-safety support when
package granularity is too broad.

2) @Nullable and @NonNull can apply to ElementType.TYPE_USE in order
to be used on generic type arguments (SPR-15942).

3) Annotations does not apply to ElementType.TYPE_PARAMETER anymore
since it is not supported yet (applicability for such use case is
controversial and need to be discussed).

4) @NonNullApi does not apply to ElementType.FIELD anymore since in a
lot of use cases (private, protected) it is not part for the public API
+ its usage should remain opt-in. A dedicated @NonNullFields annotation
has been added in order to set fields default to non-nullable.

5) Updated Javadoc and reference documentation.

Issue: SPR-15756
      1bc93e3d
  35. 18 8月, 2017 1 次提交
    • J
      Enforce non-null value from getBean and at injection points · b94302b5
      由 Juergen Hoeller 提交于 
      Bean-derived null values may still get passed into bean properties and injection points but only if those are declared as non-required. Note that getBean will never return null; a manual bean.equals(null) / "null".equals(bean.toString()) check identifies expected null values now.  This will only ever happen with custom FactoryBeans or factory methods returning null - and since all common cases are handled by autowiring or bean property values in bean definitions, there should be no need to ever manually check for such a null value received from getBean.

Issue: SPR-15829
      b94302b5
  37. 17 8月, 2017 1 次提交
  39. 20 7月, 2017 1 次提交
  41. 19 7月, 2017 2 次提交
  43. 30 6月, 2017 1 次提交
  45. 13 6月, 2017 2 次提交
  47. 12 6月, 2017 2 次提交
  49. 07 6月, 2017 1 次提交
    • J
      Consistent use of @Nullable across the codebase (even for internals) · f813712f
      由 Juergen Hoeller 提交于 
      Beyond just formally declaring the current behavior, this revision actually enforces non-null behavior in selected signatures now, not tolerating null values anymore when not explicitly documented. It also changes some utility methods with historic null-in/null-out tolerance towards enforced non-null return values, making them a proper citizen in non-null assignments.

Some issues are left as to-do: in particular a thorough revision of spring-test, and a few tests with unclear failures (ignored as "TODO: NULLABLE") to be sorted out in a follow-up commit.

Issue: SPR-15540
      f813712f
  51. 01 6月, 2017 1 次提交
  53. 31 5月, 2017 1 次提交
  55. 27 5月, 2017 1 次提交
    • S
      Introduce null-safety of Spring Framework API · 87598f48
      由 Sebastien Deleuze 提交于 
      This commit introduces 2 new @Nullable and @NonNullApi
annotations that leverage JSR 305 (dormant but available via
Findbugs jsr305 dependency and already used by libraries
like OkHttp) meta-annotations to specify explicitly
null-safety of Spring Framework parameters and return values.

In order to avoid adding too much annotations, the
default is set at package level with @NonNullApi and
@Nullable annotations are added when needed at parameter or
return value level. These annotations are intended to be used
on Spring Framework itself but also by other Spring projects.

@Nullable annotations have been introduced based on Javadoc
and search of patterns like "return null;". It is expected that
nullability of Spring Framework API will be polished with
complementary commits.

In practice, this will make the whole Spring Framework API
null-safe for Kotlin projects (when KT-10942 will be fixed)
since Kotlin will be able to leverage these annotations to
know if a parameter or a return value is nullable or not. But
this is also useful for Java developers as well since IntelliJ
IDEA, for example, also understands these annotations to
generate warnings when unsafe nullable usages are detected.

Issue: SPR-15540
      87598f48
  57. 25 1月, 2017 1 次提交
  59. 19 12月, 2016 1 次提交
  61. 24 11月, 2016 1 次提交
  63. 20 7月, 2016 1 次提交