Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • irdest-corrupted irdest-corrupted
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • we
  • irdest-corruptedirdest-corrupted
  • Issues
  • #9

Closed
Open
Created May 13, 2021 by Katharina Fey@spacekookie🏴Owner

Reduce the amount of warnings

Currently we have a lot of unused code warnings around the codebase. Some of them will go away naturally as we connect more pieces of the puzzle together, but others can be eliminated by either

  1. Deleting code that is no longer needed
  2. Making API endpoints pub that are currently only pub(crate) or similar
  3. Gating testing-only API endpoints behind #[cfg(feature = "testing")] or similar
Assignee
Assign to
Time tracking