#community-help

Non-Indexable Fields Enforced as Optional: Reasoning and Revisions

TLDR Sai asked about the enforcement of non-indexable fields being optional. Kishore Nallan informed them of the unclear historical basis and requested they create a tracking issue on GitHub for investigation.

Powered by Struct AI
5
13mo
Solved
Join the chat
Sep 14, 2022 (13 months ago)
Sai
Photo of md5-b9327d0862b35ce6892410a50cfa1514
Sai
11:46 AM
I see that there is an enforcement that non-indexable fields must be optional. Is there a reason behind this?
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
11:48 AM
To be honest, I was wondering about this myself a few weeks ago. I'm not sure how we ended up with that restriction. I think it's because of the use case that originally shaped this feature.
Sai
Photo of md5-b9327d0862b35ce6892410a50cfa1514
Sai
11:50 AM
Got it. Would be nice to have a required non-indexable field. This is not a blocker but it helps in rejecting requests which deviate from schema.
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
11:52 AM
Agreed, can you please create an issue for GH to track? I'll see if I can find some time to look into the historical reason for this decision.
Sai
Photo of md5-b9327d0862b35ce6892410a50cfa1514
Sai
11:55 AM
Sure. I’ll create an issue to track.

Thank you.