Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E extensions.typo3.org
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 79
    • Issues 79
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • 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
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • services
  • t3o sites
  • extensions.typo3.org
  • extensions.typo3.org
  • Issues
  • #251

Closed
Open
Created Sep 25, 2017 by Tobias Gülzow@guelzow

Provide examples how to create code inspections and better code quality

Hi everyone.

What kind of feature do you want?

As an extension developer, I want to make sure that my extension does not get negative badges assigned from code inspection. I also want to make sure that positive badges get assigned.

What are the benefits?

The code quality will increase significantly, if developers can check their code, before they upload their extension.

Add some use case

1.) Write a lot of code for your extension.

2.) Do a lot of testing.

3.) Let code inspection analyse the code.

4.) Fix all findings that can be fixed.

5.) Upload another release.

Tobi

Edited Sep 25, 2017 by Thomas Löffler
Assignee
Assign to
Time tracking