Lines Matching refs:in

4 The specification on types in DocBlocks (PSR-5) describes various keywords and special constructs
25 Ready to dive in and don't want to read through all that text below? Just consult the [examples](ex…
30 This component can be used in one of two ways
35 The big difference between these two is in the number of things it can resolve. 
73 The real power of this resolver is in its capability to expand partial class names into fully quali…
74 in order to do that we need an additional `\phpDocumentor\Reflection\Types\Context` class that will…
75 in which namespace the given expression occurs and which namespace aliases (or imports) apply.
79 A Fully Qualified Structural Element Name is a reference to another element in your code bases and …
90 The real power of this resolver is in its capability to expand partial element names into Fully Qua…
91 Element Names; but in order to do that we need an additional `\phpDocumentor\Reflection\Types\Conte…
92 inform the resolver in which namespace the given expression occurs and which namespace aliases (or …
118 …se that you would want to resolve (and expand) the type in the `@var` tag and the element name in …
120 …phpDocumentor\Reflection\Types\Context` with the name of the namespace and the aliases that are in 
135 object or by providing the namespace that you'd like to extract and the source code of the file in …
155 To obtain the resolved class name for the `@var` tag in the example above you can do:
166 > Why is the FQSEN wrapped in another object `Object_`?
169 > type that does not represent a Type. Also: in some cases a type can represent an "Untyped Object"…
172 Another example is on how to resolve the FQSEN of a method as can be seen with the `@see` tag in th…
180 Because Classy is a Class in the current namespace its FQSEN will have the `My\Example` namespace a…