I wrote some of the code to do this in a branch https://github.com/python-security/pyt/compare/class_based_views, but since I'm working on other things and this feature seems cool and important I'm making this issue 👍

Let me know if you would like any help in implementing.

Problem

Sometimes code elements have no package and getPackage return nulls. This introduces null checks and surprises for new developers. INRIA/spoon@84c84e1 as seen here, package can be null.

Solution

A null object[0],[1] could improve code quality. A comparable implementation is [NoSourcePosition](https://github.com/INRI

Description/ Observed Behavior

J.FieldAccess.isFullyQualifiedClassReference(MethodMatcher) allows for comparison between a FieldAccess and a MethodMatcher to see if they are describing the same fully qualified type or not.

But `Method

tophat/codewatch#1 (comment)

Our documentation currently contains only a tour, String, Map, and Int. We need to:

• Expand on the current documentation: (Types of Strings, escape characters (Strings), Map key types (Only Strings are supported), etc...).
• And also document the remainder of our core types, such as bool, or double, as well as standard methods(grab, etc...) or libraries (math, io, etc...).