[
https://issues.apache.org/jira/browse/NIFI-15678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-15678:
-------------------------------
Description: We have some rules that are tricky to adhere to such as
ExhaustiveSwitchHasDefault because the enums they operate on come from upstream
nifi-api repository, which should be decoupled from nifi. If a developer wants
to add a default to an exhaustive switch, it is good defensive programming
because a bump in dependency for nifi-api could result in a switch statement
that was previously exhaustive no longer being exhaustive, and if there is a
reasonable default, that is preferable to having to make code changes in nifi
in order to build nifi-api RCs. (was: We have some rules that are tricky to
adhere to such as ExhaustiveSwitchHasDefault because the enums they operate on
come from upstream nifi-api repository, which should be decoupled from nifi. If
a developer wants to add a default to an exhastive switch, it is good defensive
programming because a bump in dependency for nifi-api could result in a switch
statement that was previous exhaustive no longer being exhaustive, and if there
is a reasonable default, that is preferable to having to make code changes
every time the api changes.)
> Remove PMD rules related to switch statements
> ---------------------------------------------
>
> Key: NIFI-15678
> URL: https://issues.apache.org/jira/browse/NIFI-15678
> Project: Apache NiFi
> Issue Type: Task
> Reporter: Kevin Doran
> Assignee: Kevin Doran
> Priority: Minor
> Fix For: 2.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We have some rules that are tricky to adhere to such as
> ExhaustiveSwitchHasDefault because the enums they operate on come from
> upstream nifi-api repository, which should be decoupled from nifi. If a
> developer wants to add a default to an exhaustive switch, it is good
> defensive programming because a bump in dependency for nifi-api could result
> in a switch statement that was previously exhaustive no longer being
> exhaustive, and if there is a reasonable default, that is preferable to
> having to make code changes in nifi in order to build nifi-api RCs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
