Refactor the client to implement a channel navbar #76
No reviewers
Labels
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
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: gorb/frontend#76
Loading…
Add table
Add a link
Reference in a new issue
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?
closes #75
@ -68,60 +64,60 @@ const api = useApi();
const options = [
{ name: "Join", value: "join", callback: async () => {
console.log("join guild!");
what the hell did codium decide to do here? i proomise i didn't touch it
@ -0,0 +41,4 @@
</script>
<style scoped>
#navbar {
Shouldn't these variable definitions be defined in theme files?
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?
Yeah, don't see a reason not to
@ -62,1 +57,4 @@
const loading = useState("loading", () => false);
const navbar = useState<INavbar>("navbar", () => {
return {
clientItems: [
This should be an anchor element, not a button
disagree, i'd like to put an inbox here, that would be a popup, not a 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.
sure, i'm reworking it anyways
Reworking
Implement a proper navbarto wip: Implement a proper navbarwip: Implement a proper navbarto Refactor the client to implement a channel navbarokay i cannot assign you to review this
i assign you to review this
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})
Add spaces between curly brackets and content.
Arrow function doesn't need to be
async
since noawait
keyword is used.updateNavbar
doesn't seem to exist.@ -11,0 +14,4 @@
})
onActivated(async () => {
updateNavbar({isDirectMessages: true})
Add spaces between curly brackets and content.
Arrow function doesn't need to be
async
since noawait
keyword is used.