Skip to content
This repository was archived by the owner on Aug 18, 2023. It is now read-only.

Conversation

SuzGupta
Copy link
Contributor

Closes issue #163

What it Does

  • Adds a simple, hard-coded What's New view to the Settings Page so users can see the change history in the app without needing to go to the App Store listing

How I Tested

  • Launch app in simulator.
  • Tap Settings tab.
  • Tap new What's New row in new UPDATES section.
  • Behold the beautiful new and informative changelog.

Notes

  • Using Markdown plus the font modifier is perhaps overkill, but the issue said use Markdown, so I went with it.
  • The change to AWSTweet+Extension.swift was to resolve a SwiftLint trailing whitespace warning.

Screenshot

WhatsNewViewScreenRecording.mp4

Copy link
Owner

@mikaelacaron mikaelacaron left a comment

Choose a reason for hiding this comment

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

Hey @SuzGupta Can you make these changes? Thanks! If you can't by the end of Hacktoberfest, that's okay, let me know, and I can make this as hacktoberfest-accepted

I'd be interested instead of hard coding this, directly into the WhatsNewView

Comment on lines +45 to +47
HStack {
Text("What's New")
}
Copy link
Owner

Choose a reason for hiding this comment

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

This doesn't need to be in an HStack

Comment on lines +10 to +23
struct WhatsNewView: View {
var body: some View {
VStack(alignment: .leading, spacing: 10) {
Text("**v1.2**")
.font(.title3)
Text("* Delightful updates arriving soon!")
Text("**v1.1**")
.font(.title3)
Text("* Fix add folder and add tweet button not working in iOS 15")
}
.padding()
Spacer()
}
}
Copy link
Owner

Choose a reason for hiding this comment

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

Instead, I was looking for you to create a .md, markdown file, and read from that in this view, rather than hard code the changes into the View itself

Also I'd recommend putting it into a ScrollView to accommodate larger dynamic type sizes

@mikaelacaron
Copy link
Owner

Closing in place of #172

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants