You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
anthonyjoeseph
changed the title
Restrict Paths for rename, remove and upsert (Must be Performant at Compile-Time)
Restrict Paths for rename, remove and upsert
Apr 7, 2022
🚀 Feature request
Current Behavior
rename
,remove
andupsert
suggest all the same paths asget
,set
etc.Desired Behavior
rename & remove:
upsert:
Suggested Solution
This solution was proposed:
But it was determined that this caused deep type instantiation that adversely affected performance
Who does this impact? Who is this for?
users of
rename
,remove
andupsert
Describe alternatives you've considered
Worst comes to worst, we could continue to emit those keys from
Paths
but give some other type of compile-time errorAdditional context
Your environment
The text was updated successfully, but these errors were encountered: