Refactor remaining client components to SFC Setup + Composition API #130
Labels
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Depends on
#129 client: refactor radio.vue to composition api
FoundKeyGang/FoundKey
#131 client: refactor info.vue to composition api
FoundKeyGang/FoundKey
#137 client: refactor sidebar-for-mobile.vue to composition api
FoundKeyGang/FoundKey
#138 client: refactor sparkle.vue to composition api
FoundKeyGang/FoundKey
#139 refactor: token-generate-window.vue to composition api
FoundKeyGang/FoundKey
#154 client: Refactor gallery-post-preview.vue to composition API
FoundKeyGang/FoundKey
#155 client: refactor folder.vue to composition api
FoundKeyGang/FoundKey
#164 client: refactor container.vue to composition api
FoundKeyGang/FoundKey
#184 client: refactor components/tab.vue to composition API
FoundKeyGang/FoundKey
#186 client: refactor super-menu component to composition API
FoundKeyGang/FoundKey
#187 client: refactor marquee component to composition API
FoundKeyGang/FoundKey
Reference: FoundKeyGang/FoundKey#130
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is a tracking issue for any remaining uses of the old Options API or non-setup Composition API in the client codebase.
The following is a list of files that still use either the Options API or the non-
setup
version of the Composition API using the commandfind packages/client/src -name '*.vue' | xargs grep '<script' | grep -v 'setup' | cut -d ':' -f 1
:packages/client/src/components/date-separated-list.vue
⚹packages/client/src/components/form/radios.vue
⚹packages/client/src/components/form/radio.vue
(#129)packages/client/src/components/gallery-post-preview.vue
(#154)packages/client/src/components/marquee.vue
(#187)packages/client/src/components/number-diff.vue
(ebc4daa6c2
)packages/client/src/components/ripple.vue
(#181)packages/client/src/components/sparkle.vue
(#138)packages/client/src/components/tab.vue
(#184)packages/client/src/components/ui/folder.vue
(#155)packages/client/src/components/ui/info.vue
(#131)packages/client/src/components/ui/super-menu.vue
(#186)packages/client/src/components/ui/container.vue
(#164)packages/client/src/components/token-generate-window.vue
(#139)packages/client/src/ui/_common_/sidebar-for-mobile.vue
(#137)Some files listed by that command have been removed as those do have both a
setup
and a non-setup
script section.Files marked with ⚹ have a custom
render
function so it is harder (or impossible?) to refactor them to the new style.I've just had a look at
packages/client/src/components/form/radios.vue
and since it uses a custom render function and the parameters are passed in as<option>
tags and other shenanigans, I'm not sure if or how to refactor it.I thought maybe it would be possible to pass in an array of objects instead of the option tags, but the text in the options is not just plaintext, sometimes its HTML, e.g.
8d5966c0bc/packages/client/src/pages/settings/general.vue (L65-L71)
Yeah I haven't really touched any of the components that use a custom render function since I don't really know how to proceed with those.
So now all remaining components have custom render functions. The marquee one it might be possible to refactor to use
<template>
and subsequently<script setup>
, but the other ones I'm not sure if it is possible to refactor to<script setup>
at all.