Private Over Fileprivate

Reports the use of the fileprivate access-level modifier. In most cases private is the correct choice — it limits visibility to the enclosing declaration (and its extensions in the same file), which is strictly tighter.

fileprivate was introduced for the case where one type in a file needs to reach into another type in the same file. That situation is real but rare. Most properties and methods marked fileprivate could be private instead.

Replace fileprivate with private:

If the symbol really needs cross-type access inside the file, leave the modifier as fileprivate and silence the warning case-by-case.