You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We added explicit public API to the robot.api package in RF 7.2 (#5245) using redundant import aliases like from robot.parsing import get_tokens as get_tokens. That has worked well and we should now do the same with the robot root package and all sub packages. Most important reasons are:
It is in general a good idea to specify public API. Not all sub packages are part of the actual public API, but even internally explicit APIs are good.
Linters complain about normal imports that aren't used. Using redundant import aliases or __all__ avoids that, and we decided to go with the former approach earlier. We want to do linting as part of code formatting (see Automatic code formatting #5387).
Explicit package APIs ought to help with IDEs when they add automatic imports.
The text was updated successfully, but these errors were encountered:
We added explicit public API to the
robot.api
package in RF 7.2 (#5245) using redundant import aliases likefrom robot.parsing import get_tokens as get_tokens
. That has worked well and we should now do the same with therobot
root package and all sub packages. Most important reasons are:__all__
avoids that, and we decided to go with the former approach earlier. We want to do linting as part of code formatting (see Automatic code formatting #5387).The text was updated successfully, but these errors were encountered: