dwindown/wp-agentic-writer
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: Cleanup git state - commit all staged changes

Browse Source 
Major refactoring cleanup:
- Add new controller architecture (class-controller-*.php)
- Add new settings-v2 UI (views/settings-v2/)
- Add new CSS architecture (agentic-sidebar.css, tokens)
- Add esbuild build pipeline (scripts/build.js, package.json)
- Add composer dependencies (vendor/)
- Add frontend src directory (assets/js/src/index.jsx)
- Add documentation files
- Remove old/obsolete files (class-settings.php, old CSS)

This commits all pending changes from previous refactoring efforts.
This commit is contained in:
Dwindi Ramadhana
2026-06-17 05:27:58 +07:00
parent d3f142222c
commit 690991c526
7963 changed files with 941566 additions and 67372 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
vendor/phpdocumentor/reflection/docs/reflection-structure.rst vendored Normal file
View File

@@ -0,0 +1,20 @@
Reflection structure
====================
The project created by the :php:class:`\phpDocumentor\Reflection\Php\ProjectFactory` class contains a hierarchy of objects
that represent the structure of your codebase. This hierarchy includes:
Files
Each file is represented by an object of type :php:class:`\phpDocumentor\Reflection\Php\File` which contains
information about the file such as its name, path, and contents. But also the elements that are defined in the file.
Files can be accessed through the :php:method:`\phpDocumentor\Reflection\Php\Project::getFiles()` method of the project object.
Files are a flat list of all files that were analyzed, regardless of their location in the directory structure.
Namespaces
Namespaces are represented by objects of type :php:class:`\phpDocumentor\Reflection\Php\Namespace_`. Each namespace
contains a list of classes, interfaces, traits, and functions that are defined within it. Namespaces can be accessed
through the :php:method:`\phpDocumentor\Reflection\Php\Project::getNamespaces()` method of the project object.
Namespaces are hierarchical and can contain sub-namespaces.
Both namespaces and files do contain the other structural elements that are defined in them, such as classes, interfaces, traits, and functions.
This library does not provide a way to access the structure of the codebase in a searchable way. This is up to the consumer of the library to implement.