Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 985
    • Issues 985
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • Core
  • Issues
  • #2400

Closed
Open
Opened Feb 19, 2021 by eileen@eileen🎱Owner

APIv4 explorer, search kit - entity reference fields tricky if you know the id

One of my annoyances with apiv4 explorer is now in search kit too. Quite often I know the id of the contact but not other details - in order to prevent leaking information we only pass around the id. While it makes sense in most use cases to use the entity reference look up that lookup is hard to use if you just know the id as you still need to enter 'something' to make it search.

image

With search kit this could impact when making the initial search and exposing in the dashlet (I would expect we will be quickly asked for some 'search by id afflets' as well as wanting entity references in other cases. I note the afflet currently renders contact id as an integer field - which is probably better than an entity reference for our current use cases but I think that we will want to be able to have more control (ie choose between an integer or entity reference field). I can see a case for making entity reference field better support entering the contact id - but I think we need to be mindful that when people are working with contact ids they are often doing data-entry type stuff that requires them to be able to enter the id & click go without many extra steps

image

Edited Feb 19, 2021 by eileen
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
5.36.0
Milestone
5.36.0
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#2400