Rubymine interactive console has variables coming back as the pointer and not its attributes and values
已回答
Previously (before christmas break I believe) I was able to enter a variable into the debuggers interactive console and it would return what the variable contained (its attibutes and values), now if I enter it it only returns the pointer (meaning the object type and its global id).
This behaviour is not present when I interact through rails c but is when using Rubymine.
Does anyone know if this is just a setting change that I can fix or if this is something expected from a recent Rubymine change?
this is what it looks like when I call a variable now
I want to see its attributes, like in the below picture when i call on it. Thats what used to happen.
Thanks!
请先登录再写评论。
Hello,
Could you please show how it looks like for you if you call it in the Rails console not via RubyMine? Meanwhile, you can use Express evaluation for that purpose while debugging.
In console
In rubymine
Hello,
Thank you for the screenshots, I've submitted the corresponding issue on our tracker, so could you please add your vote there.
Thanks, I have!
@Olga Kuvardina
Hi, sorry for interrupting this discussion. I experienced the same issue, and it's quite annoying for me because when i debug my rails app
What i got in rubymine debugger console:
0> AdServers::TargetingVersion.last=> #<AdServers::TargetingVersion:0x00000001605d71c0>What i got in rails console:
=> #<AdServers::TargetingVersion:0x00000001202074b8id: 117,company_id: 123 ….in debug console i can't see a instant variables or fields..
I have to use inspect or express evaluation instead of easily obtaining information in the interactive console
i guess now from that issue in youtrack it's not fully undrestable what's going on.
Could i suggest to change
What happens instead?
on:
>> User.first (1.1ms) SELECT sqlite_version(*) User Load (0.3ms) SELECT "users".* FROM "users" ORDER BY "users"."id" ASC LIMIT ? [["LIMIT", 1]]=> #<User:0x000000010ea5eec0>You can add it as a comment directly to the YouTrack issue, so that we can track it better.