-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to disable readonly status of external libraries #9188
Conversation
I see the library's |
abed70d
to
6c1a020
Compare
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.
Looks like you are still missing the server implementation:
- to set the value when assets are created (via a library scan)
- to flip the flag on affected assets when the library is updated.
web/src/lib/components/photos-page/actions/delete-assets.svelte
Outdated
Show resolved
Hide resolved
@@ -201,6 +201,10 @@ export class AssetRepository implements IAssetRepository { | |||
); | |||
} | |||
|
|||
async setReadOnlyForLibrary(libraryId: string, isReadOnly: boolean): Promise<void> { | |||
await this.repository.update({ library: { id: libraryId } }, { isReadOnly }); |
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.
External libraries can have isVisible:false motion parts of extracted live photos and they need to be excluded from this update.
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.
okay. I've updated it, but you should check that I understood correctly: 3e19aef
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.
Yeah, I think that looks good. Will have to test later with motion photos to make sure are working as expected.
Hey, thanks for working on this and sorry for the confusion/back and forth around this topic. Internally we have had a lot of discussions about the direction we want to take external libraries. Long story short, we decided to go ahead with the implementation laid out in #9235. |
This is an updated version of @valpackett's #8943 with the code review comments addressed
closes #8943
closes #5449
ref #8438