ObjectValue's values stop tracing things that were parented to nil and back, until its own "Value" property gets reset

[HealthyKarl]

A private message is associated with this bug report

---

Description

This is not related to FFlagEnableRequireTracingForObjectValues but I realized there was an issue while trying that.

Let’s say you have an ObjectValue.Value set to a ModuleScript, and now suddenly you delete the ModuleScript and undo it with CTRL + Z.
Now, suddenly ObjectValue.Value becomes Instance?, even though the Instance that the ObjectValue pointed to was brought back and it still points to the same thing.

Re-production Steps

Videos attached

• Mimic this setup
  
  
• Add something like module.A = 1 into the ModuleScript, so you have something to test autocomplete with.
• Put this in the script

local test = require(script.Path1.Value)

• If you index with test. you should get an A like so:
  
  
• Now select the ModuleScript and delete it, then press CTRL + Z
• When you index test now, it will say any. But the ObjectValue is still pointing to the same thing. Which you can re-assure by right clicking the Value and clicking “Go To Reference Object”
  

 

Expected Result

The Instance the ObjectValue pointed to, was brought back. So I expect the autocomplete to work as well again?

Or some kind of way to force refresh stuff…

Actual Result

If the value that the ObjectValue points to, gets parented to nil and then back, won’t resolve its type anymore, until .Value is set empty and then pointing to the same Instance again.

 

[Yuria_theWitch]

Hi there, thank you for the report. While we understand why you would want require tracing to be able to follow through information from object values like this, this is not already intended to work. So, this should not exist as a bug report, but rather a feature request for expanding require tracing. I’ll close this issue out, but you’re welcome to open a feature request for it instead.