It's kind off unclear what is actually importing from package, it can be some classes or constants or functions. And if you use this way in your project it may be confused whch classes and constants is "yours" and whats imported from sqllex. And also namespace collisions.
Now if you see sx prefix than it's 100% clear this element is as part of sqllex package.
Yes, code becomes a little bit longer but you see where did the variables come from.
Some doc's examples (like this) have implicit imports:
It's kind off unclear what is actually importing from package, it can be some classes or constants or functions. And if you use this way in your project it may be confused whch classes and constants is "yours" and whats imported from sqllex. And also namespace collisions.
That's why I decided to change it this way:
Now if you see
sx
prefix than it's 100% clear this element is as part of sqllex package. Yes, code becomes a little bit longer but you see where did the variables come from.