Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`SaveAs` also saves the original.
See original GitHub issueDescription
When I open a document, make changes to some of its elements and later call SaveAs, the original source file also appears to be overwritten.
This happens even when I set AutoSave to false and does not happen prior to disposal.
Expected
My initial assumption was that calling SaveAs would result in the source file never being altered. Similar for example to how a save-as operation in an editor would work. There’s some degree of surprise in the current behaviour.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
For v3.0, I’m opting to remove the API as-is since it is the same as clone and has unintuitive behavior (#1376). I’d be happy to reconsider a new behavior for this post v3.0 that doesn’t have the current downfalls
As @ThomasBarnekow pointed out, this is how it was designed and would indeed take a much deeper architectural change to alter.
I agree, however, that this API is wrongly named. I’m all for suggestions and we can obsolete this one with a warning and provide an API that is better named.
Thoughts of the top of my head:
SaveAndCopyTo(...)SaveAndClone(....)Other ideas?