File modified on disk not reloaded when XAML Studio opened
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
Research direction
No files or tests are named. Start by tracing XAML Studio's caching and auto-save restore path, then compare its behavior with fresh disk content for an unmodified file. Done means reopening an unchanged file loads the latest disk version without overwriting in-progress changes.
Written by the indexing model from the issue text.
Description
If you modify a file on disk outside of XAML Studio, it is not reloaded if that file is opened in XAML Studio when XAML Studio is re-opened.
I believe this is due to the caching/auto-save mechanism in XAML Studio, we're just loading the cached content of the file vs. loading fresh content from disk of the file's state.
We should only do that in the case that the file is unmodified, as otherwise we could lose in-progress state.
A separate feature would be having a file watcher for opened files to determine if they're changed outside of XAML Studio while running and warn the user of such like other applications, should create a separate tracking issue for that...
- Dominant language
- C#
- Stars
- 450
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/XAMLStudio
-
Wrong error place Openbug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dotnet/XAMLStudio#65 · 2 comments ·
-
bug enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 38/100
dotnet/XAMLStudio#63 ·
-
bug
Difficulty 5/5 Over a week Newbie friendliness 25/100
dotnet/XAMLStudio#60 · 1 reaction ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 38/100
dotnet/XAMLStudio#56 · 1 reaction ·
-
bug
dotnet/XAMLStudio#48 · 1 assignee ·
All issues in dotnet/XAMLStudio
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·