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
The relationship between the website and SwiftUI.swift main file is confusing #2
Comments
Hi! To your two points here:
Simply add your documentation to the SwiftUI.swift file above the method you'd like to document. Currently all methods in SwiftUI.swift should be on the website, however, we have had bugs where some don't show up. Do you see any specifically that aren't showing up?
Really good idea. Will investigate how difficult it is to actually do this. But smart. |
Lmk if this clarifies your questions. If so I'll close the issue. |
|
Checkout: https://joinontap.com/view/drawinggroup%28opaque:colormode:%29 To be fair, it didn't come up when I searched it & I had to go to
Great question. We really don't have a good "triage" system right now. We recommend starting with pages that you personally want to improve. |
Thank you very much! Great project you have right here. |
Create aws.yml
TL;DR
I would like to contribute, but I am not sure how exactly the SwiftUI.swift translates into the website.
In the SwiftUI.swift file, it seems like there is an extension for every single existing Swift API, with copied paste documentation from Apple's Documentation. Obviously, the point of this project is to replace them with better, detailed, step by step documentation. But not all the methods in SwiftUI.swift shows up on the website. Will they automatically show up once the documentation is edited, or is this a manual process?
By the way, should we break up the SwiftUI.swift file into subfiles, organizing by the SwiftUI component type? Because it is kind of painful when all the previews on Github doesn't work.
The text was updated successfully, but these errors were encountered: