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

[Feature] vCard phone-number escaping #517

Merged

Conversation

workgroupengineering
Copy link
Contributor

Copy link
Owner

@kewisch kewisch left a comment

Choose a reason for hiding this comment

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

Minor changes requested, sorry for the delay!

},
"phone-number":{
fromICAL: function(aValue) {
return fmap(Array.from(aValue), c => c==='\\' ? undefined : c ).join('');
Copy link
Owner

Choose a reason for hiding this comment

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

Can you run the linters? I suspect this might fail due to missing spaces around operators.

As a bonus I'd also appreciate some performance testing to see if the conversion to and from an array is faster or slower than using indexOf and friends. I seem to recall there were some perf issues with large data sets in the past on this.

Copy link
Owner

@kewisch kewisch left a comment

Choose a reason for hiding this comment

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

A few more linter errors, see test run

@workgroupengineering workgroupengineering force-pushed the features/phone-number_escaping branch from f1b2139 to d6b2c41 Compare September 10, 2022 10:53
@kewisch kewisch force-pushed the features/phone-number_escaping branch from d6b2c41 to 9115c5d Compare October 15, 2022 21:28
Copy link
Owner

@kewisch kewisch left a comment

Choose a reason for hiding this comment

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

I adapted the changes on top of th es6 patches, either I did something wrong or there is a bug. @workgroupengineering can you double check?

@workgroupengineering workgroupengineering force-pushed the features/phone-number_escaping branch from 9115c5d to 95735e5 Compare October 17, 2022 09:40
@workgroupengineering
Copy link
Contributor Author

I adapted the changes on top of th es6 patches, either I did something wrong or there is a bug. @workgroupengineering can you double check?

I tried it on my machine it seems to work.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 3264037023

  • 0 of 13 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.003%) to 98.138%

Totals Coverage Status
Change from base Build 3257264720: 0.003%
Covered Lines: 9199
Relevant Lines: 9358

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 3264037023

  • 13 of 13 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.003%) to 98.138%

Totals Coverage Status
Change from base Build 3257264720: 0.003%
Covered Lines: 9199
Relevant Lines: 9358

💛 - Coveralls

@kewisch kewisch merged commit 3f0838c into kewisch:main Oct 18, 2022
@workgroupengineering workgroupengineering deleted the features/phone-number_escaping branch October 18, 2022 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants