Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.webbeat.web
  • Issues
  • #380
Closed
Open
Issue created Feb 03, 2016 by André Anjos@andre.anjos💬Owner

[common] Name sanitization uses lower() which may lead to unpredictable results

For some reason, our implementation of the name sanitization is not consistent. Currently, a function named sanitize_name() at (common/models.py)[beat/web/common/models.py] line 364 is somehow been called from the admin interface, but not from the user main GUI on the platform.

So, if an admin changes something on an object, its name is lower-cased and this leads to inconsistencies with the displayed object.

The admin interface should not lower the case of a valid name by default, so I think that using lower() on that line should be gone.

Can you confirm?

Assignee
Assign to
Time tracking