bert.hausmans
4f07a673a1
Vuexy/Vuetify component reference is superseded by PRIMEVUE_COMPONENTS.md
per RFC-WS-FRONTEND-PRIMEVUE. Stub forwards readers to the new doc and
provides the explicit pre-F2 SHA (1c449ff620)
for retrieving the original 777-line content during F4a–F4c on
un-migrated surfaces.
File deleted entirely in F6 cleanup. Stub-not-delete decision per
2026-05-10 project chat (Bert): explicit forwarding marker beats
git-history archaeology while parallel-mode is in force.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.3 KiB
Vuexy Components — DEPRECATED
This document is deprecated. The Crewli SPA is migrating from Vuetify to PrimeVue per RFC-WS-FRONTEND-PRIMEVUE.
During F4 component migration
The SPA contains both Vuetify and PrimeVue components simultaneously. Reference the active framework per surface:
-
For PrimeVue conventions (target state): see
PRIMEVUE_COMPONENTS.md -
For Vuetify conventions on un-migrated surfaces: see git history at commit
1c449ff6204cae6371da08c34ea8934d6b2ffcb8(HEAD ofmainimmediately before F2):git show 1c449ff6204cae6371da08c34ea8934d6b2ffcb8:dev-docs/VUEXY_COMPONENTS.md
End of life
This file is deleted entirely in F6 cleanup once F4a–F4d have migrated all surfaces to PrimeVue and F5 has validated the migration.
Why a stub instead of immediate deletion
Per project decision 2026-05-10: during F4a–F4c, some F4 developers
will need to look up Vuetify conventions for components on un-migrated
surfaces. Git-history archaeology
(git show 1c449ff6204cae6371da08c34ea8934d6b2ffcb8:dev-docs/VUEXY_COMPONENTS.md)
is workable but inconvenient. This stub provides an explicit forwarding
marker, with the actual content recoverable via git history per the
explicit SHA above.