Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • funkwhale funkwhale
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 380
    • Issues 380
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container 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
  • funkwhalefunkwhale
  • funkwhalefunkwhale
  • Issues
  • #1649
Closed
Open
Issue created Dec 18, 2021 by Marcos Peña@devilciusMaintainer

Computed properties already defined in data

Steps to reproduce

  1. Launch Funkwhale (develop version)
  2. Except for /manage/settings, visit any page at /manage/
  3. Open developer console
  4. You'll find warnings of "computed properties already defined in data"

What happens?

Computed properties defined in the Ordering mixin are also defined in the components that use that mixin.

What is expected?

No warnings

Context

When using the mixin routePreferences in ui.js should be used to define those properties.

Assignee
Assign to
Time tracking