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

fix: adding extra social link #5144

Merged
merged 4 commits into from
Sep 28, 2020
Merged

fix: adding extra social link #5144

merged 4 commits into from
Sep 28, 2020

Conversation

maze-runnar
Copy link
Contributor

Fixes #5142

scrnli_9_25_2020_10-12-57 AM

Checklist

  • I have read the Contribution & Best practices Guide.
  • My branch is up-to-date with the Upstream development branch.
  • The acceptance, integration, unit tests and linter pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

@vercel
Copy link

vercel bot commented Sep 25, 2020

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/eventyay/open-event-frontend/a79g4syv9
✅ Preview: https://open-event-frontend-git-fork-maze-runnar-social-link.eventyay.vercel.app

@auto-label auto-label bot added the fix label Sep 25, 2020
@mariobehling
Copy link
Member

Well, when adding new social links it would be good to have them here the way it is needed. We dont need a function to make all small case or caps. We just need the social links to be written in the way that the brands do it, e.g. YouTube, VK.

I am aware that this is another issue for existing links, but you are introducing new social links that do not appear as expected.

this.set('segmentedLink', {
protocol : `https://${link}.com/u/`,
address : ''
});
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This won't do. It is already highly complex, this should go as a prefix

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should just left as https://${link}.com/ for all

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, this should not happen here at all

@codecov
Copy link

codecov bot commented Sep 25, 2020

Codecov Report

Merging #5144 into development will decrease coverage by 0.07%.
The diff coverage is 100.00%.

Impacted file tree graph

@@               Coverage Diff               @@
##           development    #5144      +/-   ##
===============================================
- Coverage        22.79%   22.71%   -0.08%     
===============================================
  Files              489      489              
  Lines             5173     5181       +8     
  Branches            35       35              
===============================================
- Hits              1179     1177       -2     
- Misses            3989     3999      +10     
  Partials             5        5              
Impacted Files Coverage Δ
app/utils/computed-helpers.js 21.27% <100.00%> (ø)
app/controllers/index.js 27.27% <0.00%> (-9.10%) ⬇️
app/models/user.js 0.00% <0.00%> (ø)
app/components/forms/admin/settings/billing.js 0.00% <0.00%> (ø)
...omponents/forms/admin/settings/ticket-fees-form.js 0.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b03595c...6dd22fe. Read the comment docs.

@iamareebjamal
Copy link
Member

@mariobehling Those are internal identifiers to be saved in DB, thus need to be kept in consistent lower casing for matching purposes, there should be another mapping of the identifiers to proper cased variants

@mariobehling
Copy link
Member

@mariobehling Those are internal identifiers to be saved in DB, thus need to be kept in consistent lower casing for matching purposes, there should be another mapping of the identifiers to proper cased variants

So, that should be done in a separate issue? Please proceed as you see fit.

@iamareebjamal
Copy link
Member

No it will be done in the same PR

@iamareebjamal
Copy link
Member

Oh sorry, I thought this PR is about changing twitter to Twitter

Yes, the mapping changes will be done in that PR, not this one

@@ -31,7 +31,7 @@ export default class LinkInput extends Component {

@observes('protocol', 'address')
protocolAddressObserver() {
const link = this.linkName?.toLowerCase();
const link = this.linkName;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Restore the change please

@iamareebjamal iamareebjamal changed the title fix: adding extra Social link fix: adding extra social link Sep 28, 2020
@iamareebjamal iamareebjamal merged commit b2a0567 into fossasia:development Sep 28, 2020
@maze-runnar maze-runnar deleted the social-link branch December 13, 2020 03:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wizard Step 2: Add YouTube, VK, Weibo etc. as options for social links
3 participants