-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add content flag assets and strings #1512
Conversation
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.
Looks good. There are a couple minor changes I'm requesting, but feel free to merge after those are done.
Nos/Models/FlagOption.swift
Outdated
let description: String? | ||
var id: String { title } | ||
|
||
// `FlagOption` instances representing different categories of content that can be flagged. |
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.
// `FlagOption` instances representing different categories of content that can be flagged. | |
/// `FlagOption` instances representing different categories of content that can be flagged. |
If you make this a triple-slash (HeaderDoc comment) it will show up in the documentation pane (right hand pane of Xcode) or when this variable is option-clicked!
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.
Thank you for catching these @mplorentz
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.
I love the way this is coming along -- I like the FlagOption struct and that the content to display is all in the xcstrings file. I have a few name suggestions, but overall this looks great!
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.
I suggest renaming this radio-button-selected-bottom
(and the other radio-button-selected-top
).
@@ -5054,6 +5054,28 @@ | |||
} | |||
} | |||
}, | |||
"harassmentFlagContentDescription" : { |
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.
I think I'd switch the words around a bit, so all of them are sorted together in the file. So this one would be:
"harassmentFlagContentDescription" : { | |
"flagContentHarassmentDescription" : { |
And then all the others would be similar, starting with flagContent
and then the type and then Title
or Description
at the end.
"en" : { | ||
"stringUnit" : { | ||
"state" : "translated", | ||
"value" : "Others" |
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.
"value" : "Others" | |
"value" : "Other" |
Thanks for the naming suggestions @joshuatbrown. Honestly, I was a lil bit confused about the naming 😸. I will implement these suggestions. |
ac2ac82
to
693f7f3
Compare
# Conflicts: # Nos.xcodeproj/project.pbxproj
Issues covered
Part 1 of #1498
Description
This PR adds new colors, localised strings and a model required to display the UI of the first flow of the new moderation flow.