Closed dzzzb closed 2 years ago
Be carefull when you have a table with x obsoleted fields...
As fvet mentioned, there are cases where this might be applicable. I think it is a potential enhancement for CodeCop. I will label it for now. We are working on a process that will provide more visibility into where these issues should be filed and when they could be addressed.
Be carefull when you have a table with x obsoleted fields...
I guess you mean, in case we have Some Field
but then have to redo it as Some Field NEW
or suchlike, with e.g. a different data type (table relation, etc.), but the same caption?
If so, then yeah, it seems that obsoleted fields should not be counted to judge duplicates.
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.
Describe the bug Duplicate captions on table fields can arise from developers copying and pasting fields and forgetting to update the
Caption
to match the new field name, and this leads to confusion and possibly horror when users see two fields with the same caption and don't know which to update.To Reproduce
Expected behavior It's difficult to imagine cases where duplicate captions are legitimate, at least on tables. Maybe on pages there can be legit cases for this, but I dunno.. It's up to you whether to extend this to pages too. Here I'm concerned about tables as that's where most captions are.
Therefore, if more than one
field
s on atable
have the sameCaption
, I would think that should be a warning. Please consider adding such a diagnostic to the compiler/analysis.5. Versions: