[ 
https://issues.apache.org/jira/browse/NIFI-16101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Stieglitz updated NIFI-16101:
------------------------------------
    Description: 
Running Intellij

Analyze -> Run Inspection by Name -> Null Check Method is called with obviously 
non-null argument

indicates there are 10 places in the code where the argument for assertNotNull 
or requireNonNull are testing an argument which is not null.

The purpose of this ticket is to correct those places either by correcting the 
arguments order or by removing the assertion.

  was:
Running Intellij

Analyze -> Run Inspection by Name -> Misordered 'assertEqual' arguments

indicates there are over 100 places in the code where the arguments for 
assertEqual are not in the correct order.

The purpose of this ticket is to correct the arguments order.


> Null Check Method is called with obviously non-null argument
> ------------------------------------------------------------
>
>                 Key: NIFI-16101
>                 URL: https://issues.apache.org/jira/browse/NIFI-16101
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Daniel Stieglitz
>            Assignee: Daniel Stieglitz
>            Priority: Minor
>
> Running Intellij
> Analyze -> Run Inspection by Name -> Null Check Method is called with 
> obviously non-null argument
> indicates there are 10 places in the code where the argument for 
> assertNotNull or requireNonNull are testing an argument which is not null.
> The purpose of this ticket is to correct those places either by correcting 
> the arguments order or by removing the assertion.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to