Sass has features distinguishing files loaded from relative imports from
the entrypoints and files loaded through load paths. This is how
`quietDeps` works to ignore deprecations triggered by dependencies
rather than own code (load paths are what defines the boundary for what
is considered dependencies).
* ORM 3.4 released
* General Upgrade, 4.0 thoughts
* Finish last paragarph
* Better words
* Apply suggestions from code review
Co-authored-by: Grégoire Paris <postmaster@greg0ire.fr>
* Remove column types, auto mapping detects already.
* Fix dates to 28.6.2025 for release today
* Add second deprecated migration problem to post
---------
Co-authored-by: Grégoire Paris <postmaster@greg0ire.fr>
Static pages do not have an source to find references, so static
html links are used. Guides does see them as invalid links. This new
resolver allows us to accept the static links as valid and uses the targetreference
as url.
* Doctrine Core Team Meetup 2024 blog post
* More on sponsoring, links
* Unique blog identifier
* more fixes
* Apply suggestions from code review
Co-authored-by: Grégoire Paris <postmaster@greg0ire.fr>
* Remove 3.2.3, add Migrations 3.8.2 and explain postgresql fix.
* Apply suggestions from code review
Co-authored-by: Alexander M. Turek <me@derrabus.de>
* Apply suggestions from code review
Co-authored-by: Claudio Zizza <859964+SenseException@users.noreply.github.com>
* Update source/blog/2024-10-14-doctrine-core-team-meetup-2024.md
---------
Co-authored-by: Grégoire Paris <postmaster@greg0ire.fr>
Co-authored-by: Alexander M. Turek <me@derrabus.de>
Co-authored-by: Claudio Zizza <859964+SenseException@users.noreply.github.com>
I do not know if that was supported with doctrine/rst-parser, but there
is such a thing as a caption option for the toctree directive, and it
seems that phpDocumentor/guides supports it.
When I tried it, it produced a "p" element with a caption class.
Adding support for that means we could get rid of the toc and tocheader
directives.
These custom directives appear to be the directives that cause the most
unfixable warnings (unfixable without a custom guides extension, that
is).
We might end up with an extension anyway if there are other warnings,
but I think this could be a nice simplification.
