gorb/frontend
4
0
Fork 0
Code Issues 15 Pull requests 8 Projects Releases Packages 1 Wiki Activity Actions

Refactor the client to implement a channel navbar #76

Open
twig wants to merge 22 commits from navbar into main
pull from: navbar
merge into: gorb:main
Conversation 3 Commits 22 Files changed 13 +522 -396
twig commented 2025-08-08 00:09:54 +00:00
Owner
Copy link

closes #75

closes #75
twig added the
Kind/Feature
Priority
Medium
 labels 2025-08-08 00:09:54 +00:00
twig self-assigned this 2025-08-08 00:09:54 +00:00
twig added 2 commits 2025-08-08 00:09:54 +00:00
feat: add "Direct Messages" state to navbar
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
Details
ci/woodpecker/pr/build-and-publish Pipeline was successful
Details
89150a6cc6
requested review from sauceyred 2025-08-08 00:10:00 +00:00
twig added 1 commit 2025-08-08 00:16:46 +00:00
refactor: move logic for default icon navbar itself
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
Details
ci/woodpecker/pr/build-and-publish Pipeline was successful
Details
eb4427ff4b
twig added 2 commits 2025-08-08 00:28:21 +00:00
fix: a crash related to accessing navbar values before setup
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
Details
ci/woodpecker/pr/build-and-publish Pipeline was successful
Details
3ac8595af6
twig added 3 commits 2025-08-10 23:11:51 +00:00
chore: change type hinting syntax on navbar init
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
Details
ci/woodpecker/pr/build-and-publish Pipeline was successful
Details
74b698d728
twig reviewed 2025-08-10 23:12:44 +00:00
layouts/client.vue Outdated
@ -68,60 +64,60 @@ const api = useApi();
const options = [
{ name: "Join", value: "join", callback: async () => {
console.log("join guild!");
twig commented 2025-08-10 23:12:44 +00:00
Author
Owner
Copy link

what the hell did codium decide to do here? i proomise i didn't touch it

what the hell did codium decide to do here? i proomise i didn't touch it
twig marked this conversation as resolved
twig added 1 commit 2025-08-10 23:13:55 +00:00
chore: remove trailing new lines
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
Details
ci/woodpecker/pr/build-and-publish Pipeline was successful
Details
687d491e2a
twig added 1 commit 2025-08-10 23:14:48 +00:00
chore: remove unused navbar state reference
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
Details
ci/woodpecker/pr/build-and-publish Pipeline was successful
Details
254f7c25e3
sauceyred added 1 commit 2025-08-10 23:47:13 +00:00
feat: move initialization of navbar state variable to the initializer parameter of its definition
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
Details
ci/woodpecker/pr/build-and-publish Pipeline was successful
Details
5c38f9f9fc
sauceyred requested changes 2025-08-10 23:48:34 +00:00
Dismissed
components/UserInterface/Navbar.vue Outdated
@ -0,0 +41,4 @@
</script>
<style scoped>
#navbar {
sauceyred commented 2025-08-10 23:24:35 +00:00
Owner
Copy link

Shouldn't these variable definitions be defined in theme files?

Shouldn't these variable definitions be defined in theme files?
twig commented 2025-08-10 23:51:38 +00:00
Author
Owner
Copy link

i suppose? they're really just there to make development easier, but they could be included in the layout theme files, if so, do we include all 4?

i suppose? they're really just there to make development easier, but they could be included in the layout theme files, if so, do we include all 4?
sauceyred commented 2025-08-13 17:45:18 +00:00
Owner
Copy link

Yeah, don't see a reason not to

Yeah, don't see a reason not to
twig marked this conversation as resolved
layouts/client.vue Outdated
@ -62,1 +57,4 @@
const loading = useState("loading", () => false);
const navbar = useState<INavbar>("navbar", () => {
return {
clientItems: [
sauceyred commented 2025-08-10 23:47:36 +00:00
Owner
Copy link

This should be an anchor element, not a button

This should be an anchor element, not a button
twig commented 2025-08-10 23:52:25 +00:00
Author
Owner
Copy link

disagree, i'd like to put an inbox here, that would be a popup, not a link

disagree, i'd like to put an inbox here, that would be a popup, not a link
sauceyred commented 2025-08-13 17:44:49 +00:00
Owner
Copy link

Right but I think all clickable elements that lead you to an external site should be anchor elements. Here I'm specifically talking about the source code element.

Right but I think all clickable elements that lead you to an external site should be anchor elements. Here I'm specifically talking about the source code element.
twig commented 2025-08-13 17:45:27 +00:00
Author
Owner
Copy link

sure, i'm reworking it anyways

sure, i'm reworking it anyways
👍 1
twig marked this conversation as resolved
twig dismissed sauceyred's review 2025-08-13 17:38:10 +00:00
Reason:

Reworking

twig changed title from Implement a proper navbar to wip: Implement a proper navbar 2025-08-13 17:38:18 +00:00
twig added 9 commits 2025-08-13 19:27:10 +00:00
style: change navbar button colours on hoverr
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
Details
ci/woodpecker/pr/build-and-publish Pipeline was successful
Details
c9843bf4f2
twig changed title from wip: Implement a proper navbar to Refactor the client to implement a channel navbar 2025-08-13 19:27:42 +00:00
twig added 1 commit 2025-08-13 19:28:25 +00:00
style: rename guildnavbar to channelnavbar
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
Details
ci/woodpecker/pr/build-and-publish Pipeline was successful
Details
bb00f288f7
twig added 1 commit 2025-08-13 19:31:36 +00:00
chore: remove unused imports
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
Details
ci/woodpecker/pr/build-and-publish Pipeline was successful
Details
8acf6a77eb
twig commented 2025-08-13 19:54:21 +00:00
Author
Owner
Copy link

okay i cannot assign you to review this

i assign you to review this

okay i cannot assign you to review this i assign you to review this
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
Details
ci/woodpecker/pr/build-and-publish Pipeline was successful
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin navbar:navbar
git checkout navbar

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git checkout main
git merge --no-ff navbar
git checkout navbar
git rebase main
git checkout main
git merge --ff-only navbar
git checkout navbar
git rebase main
git checkout main
git merge --no-ff navbar
git checkout main
git merge --squash navbar
git checkout main
git merge --ff-only navbar
git checkout main
git merge navbar
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
sauceyred
Labels
Clear labels   
Compat/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
WIP

Not yet ready

No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
WIP
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
twig
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: gorb/frontend#76
No description provided.
Delete branch "navbar"

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?