-
Notifications
You must be signed in to change notification settings - Fork 72
Always use serialized text when deserializing #97
Always use serialized text when deserializing #97
Conversation
@kevinsawicki Could you take a look at this one, since you worked on the file loading/watching logic? It's seeming like it's ok to just always use the serialized text when deserializing the buffer, but I might be missing something. |
@@ -107,7 +107,6 @@ class TextBuffer | |||
@transactCallDepth = 0 | |||
@digestWhenLastPersisted = params?.digestWhenLastPersisted ? false | |||
@modifiedWhenLastPersisted = params?.modifiedWhenLastPersisted ? false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think @modifiedWhenLastPersisted
can be removed now too, it appears unused
This looks okay to me, I'm not 100% sure why these nuances were there previously but if the specs are green then I'm good with this. I did leave one minor comment about another piece of serialized state that could possibly be removed now as well since it is unused. |
Conflicts: package.json
9501792
to
f3fa3d0
Compare
…ation Always use serialized text when deserializing
I realized that the fix added in #95 doesn't always work. When the file was saved, the undo history was still lost on reload. This fixes that.
Depends on atom/node-pathwatcher#85