-
-
Notifications
You must be signed in to change notification settings - Fork 304
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
feat: add share_button_visible option #403
Conversation
I would change the wording. It is untrue that you are preventing the sharing if you untick the box. I would say something more in the like "display social media sharing links". I think you are missing define(BOOL, '0|1'); in your migration file. |
@ildyria
OK. |
@ildyria
As you notice my English is not good. Please tell me if you come up with better naming. I will update again and again :) ScreenshotsOthresShould I squash and force push? Thank you :) |
No need, we usually directly "Squash and merge" the PR. :) |
I'm working on tmp-hallenser PR and then I'll look at yours. 👍 |
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.
Lokks pretty good to me. 😃
Description
I have already read #293. I have the same opinion with @CountCypher.
I want to publish my photo with public permission but I don't want the lychee to appear the share button.
Yes, I can delete that element if I edit & build https://github.com/LycheeOrg/Lychee-front. But,
I don't want to do it. Because, if I fork it I have to sync upstream with my forked repo.
Implementation
I implemented this option naming to
sharable
. It behaves just like downloadable.The current public album & photo will be
sharable = true
automatically when migrate the database.Others
Maybe I can't backport to this feature to less than v4.
Thank you :)