Refactor the client to implement a channel navbar #76

Merged
temmie merged 25 commits from navbar into main 2025-08-15 12:18:24 +00:00
Owner

closes #75

closes #75
temmie added the
Kind/Feature
Priority
Medium
labels 2025-08-08 00:09:54 +00:00
temmie self-assigned this 2025-08-08 00:09:54 +00:00
temmie 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
ci/woodpecker/pr/build-and-publish Pipeline was successful
89150a6cc6
requested review from sauceyred 2025-08-08 00:10:00 +00:00
temmie 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
ci/woodpecker/pr/build-and-publish Pipeline was successful
eb4427ff4b
temmie 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
ci/woodpecker/pr/build-and-publish Pipeline was successful
3ac8595af6
temmie 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
ci/woodpecker/pr/build-and-publish Pipeline was successful
74b698d728
temmie reviewed 2025-08-10 23:12:44 +00:00
@ -68,60 +64,60 @@ const api = useApi();
const options = [
{ name: "Join", value: "join", callback: async () => {
console.log("join guild!");
Author
Owner

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
temmie marked this conversation as resolved
temmie 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
ci/woodpecker/pr/build-and-publish Pipeline was successful
687d491e2a
temmie 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
ci/woodpecker/pr/build-and-publish Pipeline was successful
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
ci/woodpecker/pr/build-and-publish Pipeline was successful
5c38f9f9fc
sauceyred requested changes 2025-08-10 23:48:34 +00:00
Dismissed
@ -0,0 +41,4 @@
</script>
<style scoped>
#navbar {
Owner

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

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

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?
Owner

Yeah, don't see a reason not to

Yeah, don't see a reason not to
temmie marked this conversation as resolved
@ -62,1 +57,4 @@
const loading = useState("loading", () => false);
const navbar = useState<INavbar>("navbar", () => {
return {
clientItems: [
Owner

This should be an anchor element, not a button

This should be an anchor element, not a button
Author
Owner

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
Owner

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.
Author
Owner

sure, i'm reworking it anyways

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

Reworking

temmie changed title from Implement a proper navbar to wip: Implement a proper navbar 2025-08-13 17:38:18 +00:00
temmie added 9 commits 2025-08-13 19:27:10 +00:00
temmie 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
temmie 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
ci/woodpecker/pr/build-and-publish Pipeline was successful
bb00f288f7
temmie 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
ci/woodpecker/pr/build-and-publish Pipeline was successful
8acf6a77eb
Author
Owner

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
temmie added 1 commit 2025-08-14 17:37:12 +00:00
Merge remote-tracking branch 'origin/main' into navbar
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
ci/woodpecker/pr/build-and-publish Pipeline was successful
bd895c9a34
sauceyred requested changes 2025-08-15 09:39:01 +00:00
Dismissed
sauceyred left a comment
Owner

Review comments.
Also, I'm not a big fan of the navbar going all the way to the right edge when it doesn't on the left. Maybe we should have separate guild and client navbars?

Review comments. Also, I'm not a big fan of the navbar going all the way to the right edge when it doesn't on the left. Maybe we should have separate guild and client navbars?
@ -10,1 +10,4 @@
import DirectMessagesSidebar from '~/components/Me/DirectMessagesSidebar.vue';
onMounted(async () => {
updateNavbar({isDirectMessages: true})
Owner

Add spaces between curly brackets and content.
Arrow function doesn't need to be async since no await keyword is used.
updateNavbar doesn't seem to exist.

Add spaces between curly brackets and content. Arrow function doesn't need to be `async` since no `await` keyword is used. `updateNavbar` doesn't seem to exist.
temmie marked this conversation as resolved
@ -11,0 +14,4 @@
})
onActivated(async () => {
updateNavbar({isDirectMessages: true})
Owner

Add spaces between curly brackets and content.
Arrow function doesn't need to be async since no await keyword is used.

Add spaces between curly brackets and content. Arrow function doesn't need to be `async` since no `await` keyword is used.
temmie marked this conversation as resolved
temmie added 2 commits 2025-08-15 10:29:04 +00:00
style: change member list and navbar colours
All checks were successful
ci/woodpecker/push/build-and-publish Pipeline was successful
ci/woodpecker/pr/build-and-publish Pipeline was successful
ci/woodpecker/pull_request_closed/build-and-publish Pipeline was successful
628a40f2b8
requested review from sauceyred 2025-08-15 10:29:34 +00:00
sauceyred approved these changes 2025-08-15 12:17:17 +00:00
temmie merged commit 5adae3b380 into main 2025-08-15 12:18:24 +00:00
temmie deleted branch navbar 2025-08-15 12:18:25 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
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: gorb/frontend#76
No description provided.