Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Briar Desktop Briar Desktop
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 175
    • Issues 175
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • briar
  • Briar DesktopBriar Desktop
  • Issues
  • #315

Closed
Open
Created Feb 21, 2022 by Mikolai Gütschow@ialokimMaintainer0 of 1 task completed0/1 task

Use private Composable functions where possible

The following discussion from !165 (merged) should be addressed:

  • @sebkur started a discussion: (+2 comments)

    Hmm, I guess [having private Composable functions has] been possible all the time, we just haven't made use of it the way one usually would. For example looking at PrivateMessageScreen, all methods except PrivateMessageScreen() could be private. I think that's pretty common in our codebase. I think we didn't stumble upon it as IntelliJ doesn't warn about @Composable functions that could be private like it does with regular methods that could be private.

Assignee
Assign to
Time tracking