Skip to content
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

Merged
merged 9 commits into from
Dec 23, 2019

Conversation

yoshinorin
Copy link
Contributor

@yoshinorin yoshinorin commented Dec 7, 2019

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 :)

@ildyria
Copy link
Member

ildyria commented Dec 9, 2019

I would change the wording.
"Visitors of your gallery can share this album."

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.

@yoshinorin
Copy link
Contributor Author

@ildyria
Thank you :)
I was just about to fix define(BOOL, '0|1');.

I would change the wording.
It is untrue that you are preventing the sharing if you untick the box.

OK.
I will change all of sharable (database value, variable name, etc) to another naming as well.

@yoshinorin yoshinorin changed the title feat: add sharable option [WIP] feat: add sharable option Dec 9, 2019
@codecov-io
Copy link

codecov-io commented Dec 14, 2019

Codecov Report

Merging #403 into master will increase coverage by 1.21%.
The diff coverage is 61.53%.

@yoshinorin
Copy link
Contributor Author

@ildyria
I updated PR and add some fixes.

  • sharable to share_button_visible
    • I was wondering whether to use the word visibility. However, I think visibility can take values other than bool(true, false), So, I decide to use visible
  • Return share_button_visible from PhotoController.
    • I forgot to update PhotoController when I first time submitted this PR
  • Update all languages explanation.
    • Just copy English
    • Should I translate all language using by Google Translate?

As you notice my English is not good. Please tell me if you come up with better naming. I will update again and again :)

Screenshots

sb1

sb2

sb3

Othres

Should I squash and force push?

Thank you :)

@yoshinorin yoshinorin changed the title [WIP] feat: add sharable option feat: add share_button_visible option Dec 15, 2019
@ildyria
Copy link
Member

ildyria commented Dec 16, 2019

Should I squash and force push?

No need, we usually directly "Squash and merge" the PR. :)

@ildyria
Copy link
Member

ildyria commented Dec 16, 2019

I'm working on tmp-hallenser PR and then I'll look at yours. 👍

@ildyria ildyria requested review from ildyria, kamil4, tmp-hallenser and d7415 and removed request for ildyria and kamil4 December 16, 2019 14:14
Copy link
Member

@ildyria ildyria left a 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. 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants