Native Create Issue #311
Native Create Issue #311
Conversation
Still looks like 💩 - If anyone wants to give a hand making it look nice I would appreciate it 😅 |
I'd say for an initial implementation I'm happy with it now - Obviously we can add new functionality down the line for adding labels, assignees etc (assuming you have push permissions) but I think this is good? |
@BasThomas You're more than welcome to branch off and try match that! It looks a look more modular, and similar to Eureka just couldn't see a nice way of doing it without ballooning hence with the simpler scroll view |
Will give this a deeper look soon, def need to massage the design. I personally prefer the look of the stuff @BasThomas posted: grouped |
Design has never been a hotspot of mine, and editing tools are definitely up for discussion (I basically just copied what we had already to minimise on work!) This does look quite nice though: http://1writerapp.com/ If someone wants to pick up the design then I'd be appreciative - otherwise I can try and copy BasThomas' design above |
Probably also want to add this option for repos you’re browsing via search. Will create a separate issue. |
This is available via search and for report a bug - am I missing something @BasThomas Sent with GitHawk |
@@ -48,6 +48,30 @@ PrimaryViewController { | |||
feed.viewDidLoad() | |||
feed.adapter.dataSource = self | |||
title = "\(repo.owner)/\(repo.name)" | |||
|
|||
if repo.hasIssuesEnabled { | |||
navigationItem.rightBarButtonItem = UIBarButtonItem( |
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.
@BasThomas You mean like this code here 😉
I know I need to move it to the action sheet, but the logic is all here to have a "New Issue" button for the repo view controller - Just don't merge master into this branch 😂
# Conflicts: # Classes/Repository/RepositoryViewController.swift # Resources/Info.plist
@rnystrom Just updated with changes in master so the "Create Issue" is now in the overflow rather than it's own button In terms of design, https://github.com/xmartlabs/Eureka would give us a basic form with all the structure done for us -- Would this be a solution you're okay with? |
Is that project gonna be overkill tho? Will we use it for more stuff in the future? Nervous about taking another dependency for a simple design. Sent with GitHawk |
Further down the line I'm sure the form will get more complicated with files/images, labels, assignees, etc Other forms include add/edit projects, maybe even editing repos I'll give it a quick go now without Eureka and see how it ends up |
You mentioned before that we need to come up with a better way of doing markdown so I left the buttons out of this design. Is this what you had in mind? |
cc @BasThomas ^^ also |
Ya that looks pretty great, nice and simple. We should be able to add the markdown actions as the input accessory view, right? @Sherlouk can you confirm that's still possible here? |
It should still be possible yea (it’s just a text view!) will look into it Sent with GitHawk |
# Conflicts: # Classes/Repository/RepositoryViewController.swift # Resources/Info.plist
Added markdown controls ^^ |
Yessss! |
@rnystrom We waiting on anything to merge this now? 😄 |
Nice! |
@rnystrom Hit me up when ready to merge and I can deal with the conflicts |
@Sherlouk give it a go and DM me on Twitter so I can merge ASAP to avoid more conflicts! |
@rnystrom Picking this up now, will be 5 minutes |
# Conflicts: # Classes/Repository/RepositoryViewController.swift # Classes/Settings/SettingsViewController.swift # Resources/Info.plist
All good! |
May I ask why you have chosen a |
Originally it was a In the end it came down to simplicity and "out of the box" design. A grouped In this situation there was very little flexibility required, though when we do get the point of adding additional fields, such as labels, this may have to change. |
Closes #288
Closes #350
Example output: rnystromtest/Githawk-Playground#2
Used API: https://developer.github.com/v3/issues/#create-an-issue