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(*): Style updates, add edit issue body functionality #409
fix(*): Style updates, add edit issue body functionality #409
Conversation
@@ -172,6 +173,28 @@ export const editIssueComment = (issueCommentId, owner, repoName, body) => { | |||
}; | |||
}; | |||
|
|||
export const editIssueBody = (owner, repoName, issueNum, body) => { |
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.
editIssue
currently already exists and I'm definitely not a fan of how I'm passing updateParams
to it. Because the comment is HTML, can't leverage that to pass in a new update parameter for the text to replace state.
Will need to refactor how editIssue
works later without a doubt and instead of passing in updateParams, just get what's returned from the API (and we can then just remove this)
And why are they needed? There in fact there is an alignment on the center, and after addition padding, any more will not be absolutely on the center to be displayed. |
@housseindjirdeh User titles are needed, at least for searched result or stared repositories. This feature is added by #254 in particular. And I also mentioned the redundancy, but you missed it. :) |
Seconding @lex111, let's use that emoji and bring back username/reponame : If I'm on some user profile, then check his repos, I'll have to remember the user name, or navigate back and forth to have the repo full name to clone it |
@@ -63,7 +63,7 @@ const renderTitle = repository => | |||
<View style={styles.repositoryContainer}> | |||
<View style={styles.titleWrapper}> | |||
<Text style={styles.title}> | |||
{repository.full_name} | |||
{repository.name} |
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.
As correctly noted, displaying only the name of the repository will not be convenient, so we need to add a check: if this is an auth screen, then show only the name of the repository, and if the user profile, then display the full name.
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.
Although, maybe it can just add the lock
icon (if private) to the end of the title?
@chinesedfan so in fact will work?
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.
Yes, it doesn't matter the pending element is the private box or the lock icon, as long as the parent element is Text and the child view has width&height specified.
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.
Done
@housseindjirdeh What do you think about handling with edit issue body in another screen. Maybe we could create an |
Honestly I just felt that the message looks a bit squeezed for English copy? Probably just imagining things, reverted it back and removed that padding :)
Have no idea how I missed that point. Thank you, and I completely forgot that
Done: |
@jouderianjr so you make a good point, and right now if you head to the settings screen you can modify a few issue settings (but not title or description) We could have issue title and description modifiable here but honestly I actually prefer at least the description being modified the same way as any other comment. It feels intuitive as I still think of it as a comment. Definitely curious if you think there's a better option however, as well as how we can add functionality to edit the issue title in the future 🤔 |
Oops, did not notice if padding left and right, then this should not affect the alignment, although at first glance it seemed to me that this is so. Excuse me, let's it return, but can we make them smaller? |
Do not you think that the size is big? In my opinion it was better if you reduce the size of the icon? |
Cheers no worries. Added some padding but reduced it a bit :)
And nice you're probably right. Reduced it: |
@housseindjirdeh I'd rather use type="default" (or no type) for the "Mark all as read" button. |
Done. Although the default button looks interesting 🤔 Are these the intended colors @machour? (just showing it defaulted for the merge button for demo, don't have any notifications in the moment that's why :)) |
@housseindjirdeh that icon should be black, otherwise it's the intended look. |
I got it, make sense, so we can release that in v1.3 and then reorganize this screen in order to fit edit title and body 😄 Nice job mate! |
97812ec
to
ed1d828
Compare
@@ -188,7 +191,12 @@ export class Button extends Component { | |||
}} | |||
disabledStyle={disabledStyle} | |||
icon={ | |||
icon && { ...defaultIconStyle, ...sizes[size].iconStyle, ...icon } | |||
icon && { | |||
...defaultIconStyle, |
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.
Extended this since didn't seem like icons were being styled in the component within @machour
@machour fixed: |
@jouderianjr Exactly what I was thinking :) |
Various fixes/updates for #381
IssueDescriptionListItem
better in terms of boldnessprivate
box being squeezed anymore as most repo titles aren't nearly as long)