import-explicit-visibility

Available in: KerML, SysML

This checks that imports have an explicit visibility.

The specification requires explicit visibility at the grammar level. However, for consistency with all the other relationships and improved diagnostics, Syside allows omitting visibility and instead emits a clear diagnostic during validation.

Example

import ScalarValues::Boolean; // error

Fix this by specifying private, protected, or public visibility:

private import ScalarValues::Boolean; // ok

Note that root level imports must be private.