Skip to content

Conversation

@tissak
Copy link

@tissak tissak commented Feb 19, 2014

Had an object that had an instance variable that came in at runtime via another gem. No getters / setters as it was not one of the values I cared about preserving. However the system would explode trying to fetch and restore the state of this variable.

Changes will ensure the getter / setter methods exist before we try to call them. It does let variable state drop away though so have made a slight change to the readme to express this. I feel it's valid that you ensure there are accessors for the variable states you want to preserve.

Longer term maybe look at instance variable get / set directly if it's worth pursuing full variable state preservation.

tissak added 3 commits February 19, 2014 10:49
…essors. Not all instance variables have accessors so be defensive. At this point if you are looking to preserve a state you should have an attr_accessor for it.
Be clear about what is stored and recovered.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant