nextcloud / nextcloud/circles

unable to set properly displayName

Open
#1,266 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
177
Forks
68
Avg merge
2d 22h
Merged PRs (30d)
60

Description

I'm using NC 24.0.1 and Circles 24.0.0.

I've created a Collective named "Communication", but the associated Circle is name "Communication (2)". I don't know why "(2)" has appeared.

Here is the details of the Circles:

{
    "id": "PQviA6t3NOtZYlcOkjBw5Rf8rycNJpQ",
    "name": "Communication",
    "displayName": "Communication (2)",
    "sanitizedName": "Communication", [...]
}

I tried to change the displayName using occ:
occ circles:manage:edit PQviA6t3NOtZYlcOkjBw5Rf8rycNJpQ displayName Communication

but it does not work, I've got still "Communication (2)" as a displaName.

But when I do:
occ circles:manage:edit PQviA6t3NOtZYlcOkjBw5Rf8rycNJpQ displayName Communication1

I've got:

{
    "id": "PQviA6t3NOtZYlcOkjBw5Rf8rycNJpQ",
    "name": "Communication1",
    "displayName": "Communication1",
    "sanitizedName": "Communication1",
}

Then exec again:
occ circles:manage:edit PQviA6t3NOtZYlcOkjBw5Rf8rycNJpQ displayName Communication

it reverts back to:

{
    "id": "PQviA6t3NOtZYlcOkjBw5Rf8rycNJpQ",
    "name": "Communication",
    "displayName": "Communication (2)",
    "sanitizedName": "Communication", [...]
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the two occ circles:manage:edit commands shown in the issue and inspect how the circle's displayName is handled when changing it to Communication. Done means setting that value no longer restores Communication (2), while the existing change to Communication1 continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.