Closed dzzzb closed 2 years ago
Thanks for reporting this issue. Sorry we haven’t completed it yet, but we’ve had to prioritize elsewhere. We’re planning to give the CodeCop engine and its rules an overhaul in a future major release. Thanks for your patience.
This rule correctly catches non-FlowField/-Blob fields passed to
CalcFields()
, but it does not warn forSetAutoCalcFields()
, instead resulting in a runtime error. It should warn for both, thus stopping developers from publishing a wrongSetAutoCalcFields()
and only finding out later.Saying that: if the current diagnosed case is a runtime error, why is it only a compile-time warning? If that code cannot possibly work at runtime, don't let devs think they can ignore the 'warning', because it will just be transmuted into an error later, thus again wasting our time. That is: make any such attempt to calc a non-flowfield be a compile error
Edit: This should also apply to other places where one can specify
CalcFields
, e.g. in aReport
dataitem
. Please ensure that it does.