When the caret is at such a parameter, the IDE offers a quick-fix to explicitly declare the inferred annotation:įinally, there are many brand new inspections, which you can easily see in Settings by typing "2017.3" in the Search field: JVM Debugger The IDE shows the inferred annotations in Parameter Info and Quick Doc popups. Now it also infers nullability annotations for parameters of sealed and private methods: Earlier annotations were inferred only for library methods' parameters and for any methods' return types. We've improved the way nullability annotations are inferred. The data flow analysis for the Optional type has also become smarter and now reports even non-obvious issues: Usages of StringBuilder can now be replaced with llect and Collectors.joining:Ĭode that iterates to find a maximum or a minimum can now be automatically replaced with Stream.max and Stream.min: The quick-fixes that help migrate plain for loops to Stream API have been extended to cover a few more sophisticated but quite common cases. IntelliJ IDEA 2017.3 now detects possible nullability issues, even in Stream API call chains: Javaįirst of all, we continue enhancing our data flow analysis for Java code. Let's talk about them in a bit more detail. In the announcement, we briefly mentioned some of the major changes the update will deliver. Last week, we announced the opening of the EAP for IntelliJ IDEA 2017.3, the upcoming IDE update that will be released this fall.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |