AkkomaGang/admin-fe
6
2
Fork 7
Code Issues 7 Pull requests 2 Projects Releases Wiki Activity

add extra frontend columns for 3rd party FEs #28

Merged
floatingghost merged 1 commit from 3rd-part-fe into develop 2025-11-28 16:52:22 +00:00
Conversation 1 Commits 1 Files changed 6 +17195 -12675
floatingghost commented 2025-11-22 17:18:52 +00:00
Owner
Copy link

looks like this yesyes

looks like this yesyes
Snapshot_2025-11-22_17-18-36.png
93 KiB
Snapshot_2025-11-22_17-18-36.png 
update yarn, resolutions, frontend table
Oneric reviewed 2025-11-22 22:36:51 +00:00
src/views/settings/components/inputComponents/FrontendsTable.vue
@ -18,0 +30,4 @@
>
<template slot-scope="scope">
<a v-if="scope['row']['bugtracker']" :href="scope['row']['bugtracker']" target="_blank">{{ scope['row']['bugtracker'] }}</a>
<a v-else href="https://akkoma.dev">akkoma.dev</a>
Oneric commented 2025-11-22 22:36:51 +00:00
Owner
Copy link

Not sure if relevant enough so do feel free to dismiss, but (when not already logged in) https://akkoma.dev redirects specifically to the backends repo and mayyyyybee(?) might mislead some to file issues about various frontends against the backend?

Perhaps we could fall back to the git URL if no tracker is set or just always fill out bugtracker even for first-party FEs?

Not sure if relevant enough so do feel free to dismiss, but (when not already logged in) `https://akkoma.dev` redirects specifically to the backends repo and _mayyyyybee(?)_ might mislead some to file issues about various frontends against the backend? Perhaps we could fall back to the `git` URL if no tracker is set or just always fill out `bugtracker` even for first-party FEs?
floatingghost commented 2025-11-22 22:53:49 +00:00
Author
Owner
Copy link

hmmm perhaps just filling in bug tracker for everything makes most sense

hmmm perhaps just filling in bug tracker for everything makes most sense
Oneric commented 2025-11-22 22:54:11 +00:00
Owner
Copy link

will do

will do
Oneric commented 2025-11-22 23:01:06 +00:00
Owner
Copy link

though, swagger-ui is a bit odd here: actual issues with the FE itself should in principle be reported to the upstream project, but issues with our API definitions (like: AkkomaGang/akkoma#813 ) to the akkoma backend. Furthermore, the particular swagger build we ship is probably pretty outdated and thus even for actual swagger-inherent issues perhaps not too useful for the upstream project.
Not sure what bugtracker to put here

though, `swagger-ui` is a bit odd here: actual issues with the FE itself _should_ in principle be reported to the upstream project, but issues with our API definitions (like: https://akkoma.dev/AkkomaGang/akkoma/issues/813 ) to the akkoma backend. Furthermore, the particular swagger build we ship is probably pretty outdated and thus even for actual swagger-inherent issues perhaps not too useful for the upstream project. Not sure what bugtracker to put here
floatingghost commented 2025-11-23 14:01:57 +00:00
Author
Owner
Copy link

probably just the backend one honestly, I don't think many people even use it beyond me for testing

probably just the backend one honestly, I don't think many people even use it beyond me for testing
Oneric commented 2025-11-23 16:06:50 +00:00
Owner
Copy link

done in the backend PR

done in the backend PR
Oneric marked this conversation as resolved
floatingghost deleted branch 3rd-part-fe 2025-11-28 16:52:22 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AkkomaGang/admin-fe!28
No description provided.