Excess field shown in INTERFACE

[stefjoosten]

Suppose I have a field in an interface

CONTEXT IssuePrototype110

RELATION usedAt[Thing*Location]
 = [ ("o1", "L1")
   , ("o1", "L2")
   , ("o1", "L3")
   ]
   
INTERFACE Things : "_SESSION"[SESSION];V[SESSION*Thing] BOX
   [ things : I ]

INTERFACE Ifc FOR User: I[Thing] BOX
   [ "used at " : usedAt[Thing*Location] cRUd
   ]

ENDCONTEXT

In this example, the user cannot create new locations (c is lowercase) and the relation usedAt supports multiple locations per Thing (usedAt is not univalent).

In my browser, this is what I see in INTERFACE Ifc:

Feature request

I would like to see the "Add Location" field only if there is something to add. In this example, there is nothing to add and the empty box unjustly suggests that I can add a location.

So, in case the CRUD of a field forbids creation and allows update, and the population shown contains all elements of the concept, do NOT display a field to add an atom.

[Michiel-s]

I believe this is already picked up in the new frontend.

I'll do the check. Should be implemented in AtomicObjectComponent.

[stefjoosten]

@Michiel-s did you do the check? Can we close this?

[Michiel-s]

It is implemented, but there is a bug I think. The ngIf for hiding the dropdown box uses a different options list compared to the filtered list for the options.

So currently the options don't show the items that are already included in the relation (that is good), but the dropdown is not hidden is there are no options.