Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
This repository was archived by the owner on Jun 7, 2020. It is now read-only.

[BLOCKED][IMPROVEMENT] Remove markdown & parse emojis in push notifications #2432

Open
cardoso wants to merge 6 commits into develop
base: develop
Choose a base branch
Loading
from imp/remove_md_pn

Conversation

@cardoso
Copy link
Member

@cardoso cardoso commented Dec 14, 2018
edited
Loading

@RocketChat/ios

Had to move some stuff around to share markdown code with the extension

Partially closes #1563
Blocked by RocketChat/Rocket.Chat#12956

parser.strikeAttributes = [NSAttributedString.Key.strikethroughStyle.rawValue: NSNumber(value: NSUnderlineStyle.single.rawValue)]
parser.linkAttributes = [NSAttributedString.Key.foregroundColor.rawValue: UIColor.darkGray]

#if !EXCLUDE_MARKDOWN_DOWNLOAD
Copy link
Contributor

Choose a reason for hiding this comment

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

I love the idea of using this kind of configuration per scheme, but what about something "pattern", like this?

ROCKETCHAT_MARKDOWN_DOWNLOAD_MEDIA

This way we:

  1. Make sure the name is actually managed by us;
  2. It's a positive checking, not negative, will be like this:
#if ROCKETCHAT_MARKDOWN_DOWNLOAD_MEDIA
...
#endif

I think it brings more clarity to the code... what do you think?

Copy link
Member Author

Choose a reason for hiding this comment

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

  1. Agreed with namespacing the flag
  2. If positive then we have to remember to add it for every build configuration in every target :/ this is very specific for the Notification Service Extension to avoid including all our download related classes.

]
}

// swiftlint:enable all
Copy link
Contributor

Choose a reason for hiding this comment

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

👀

Copy link
Member Author

Choose a reason for hiding this comment

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

I decided to treat this file as an external library. It has tons of single letter variables that prevent compiling with our linter.

Should I rewrite it? What do you think?

@cardoso cardoso changed the title (削除) [BLOCKED][IMPROVEMENT] Remove markdown from push notifications (削除ここまで) (追記) [BLOCKED][IMPROVEMENT] Remove markdown & show emojis in push notifications (追記ここまで) Dec 21, 2018
@cardoso cardoso changed the title (削除) [BLOCKED][IMPROVEMENT] Remove markdown & show emojis in push notifications (削除ここまで) (追記) [BLOCKED][IMPROVEMENT] Remove markdown & parse emojis in push notifications (追記ここまで) Dec 21, 2018
@rafaelks rafaelks modified the milestones: 3.3.0, 3.5.0 Mar 22, 2019
@rafaelks rafaelks modified the milestones: 3.4.1, 3.5.0 Apr 5, 2019
@rafaelks rafaelks modified the milestones: 3.5.0, 3.6.0 May 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

2 more reviewers

@rafaelks rafaelks rafaelks left review comments

@houndci-bot houndci-bot houndci-bot left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Projects

None yet

Milestone

3.6.0

Development

Successfully merging this pull request may close these issues.

[IMPROVEMENT] Remove Markdown tags from in some parts of the app

AltStyle によって変換されたページ (->オリジナル) /