Markers
Table of Contents
Linker.php
Type | Line | Description |
---|---|---|
TODO | 233 | Can we find another solution for this? |
NamespaceTreeBuilder.php
Type | Line | Description |
---|---|---|
TODO | 88 | find out why this can happen. Some bug in the assembler? |
ArgumentDescriptor.php
Type | Line | Description |
---|---|---|
TODO | 39 | Apparently, in our Mario's example this can be null. But that is weird. Investigate this after |
FunctionAssembler.php
Type | Line | Description |
---|---|---|
TODO | 73 | this looks like a potential bug. Have to investigate this! |
MethodAssembler.php
Type | Line | Description |
---|---|---|
TODO | 45 | Uncomment this line as soon as DocBlockReflection 5.4 is released and included |
IsTyped.php
Type | Line | Description |
---|---|---|
TODO | 37 | update link to point to the final destination for the PHPDoc Standard. |
ProjectDescriptorBuilder.php
Type | Line | Description |
---|---|---|
TODO | 166 | Any change in the API Specification compared to a previous (cached) run should invalidate that cache. |
TODO | 169 | The setVisibility call should purge the cache; but once we are here, cache has already been loaded.. |
TODO | 183 | This call should purge the cache; but once we are here, cache has already been loaded.. |
HasProperties.php
Type | Line | Description |
---|---|---|
TODO | 54 | check whether this function works properly, the business logic feels off somehow |
RenderHandler.php
Type | Line | Description |
---|---|---|
TODO | 58 | This is a hack; I want to rework path handling for guides as the Environment, for example, |
Transform.php
Type | Line | Description |
---|---|---|
TODO | 164 | the guides to need this, can we get rid of these lines? |
RenderGuide.php
Type | Line | Description |
---|---|---|
TODO | 87 | Extract this, as this code is duplicated |
ArrayOfTypeAdapter.php
Type | Line | Description |
---|---|---|
TODO | 29 | How and why is this adapter used? The assumption in the supports method is weird and that this adapter involves arrays is oddly specific. Is this a potential bug? |
UrlGenerator.php
Type | Line | Description |
---|---|---|
TODO | 43 | Why is this a separate URL Generator on top of the Router, specific for the LinkRenderer? Are we missing a concept? At the moment, I am not going into this because my PR is getting too big already and I keep existing behaviour, but discovering why this Url Generator even exists could improve the codebase. |
TODO | 95 | of course this is not correct, but phpDocumentor does not have a mechanism yet for determining the |
TODO | 103 | of course this is not correct, but phpDocumentor does not have a mechanism yet for determining the |
TODO | 114 | This is copied from the TableOfContentsBuilder; once we get proper support for Versions, |
TODO | 130 | Add Support for DocumentEntries to the router |
LinkRenderer.php
Type | Line | Description |
---|---|---|
TODO | 158 | Because the renderer uses an immutable pattern to change itself; the $this references |
RelativePathToRootConverter.php
Type | Line | Description |
---|---|---|
TODO | 58 | References can only point to an element that is a class, interface, trait, method, property or class constant at this moment. This is because an FQSEN does not contain the necessary data to distinguish whether the FQCN is actually a class or a namespace reference. As such we assume a class as that is the most common occurrence. |
Twig.php
Type | Line | Description |
---|---|---|
TODO | 214 | replace env with origin filesystem, as this will help us to copy assets. |