Exhibition icon indicating copy to clipboard operation
Exhibition copied to clipboard

A framework and generator for displaying SwiftUI component libraries

Results 21 Exhibition issues
Sort by recently updated
recently updated
newest added

Code documentation should be added to all public members. Some sort of generator (eg swiftdocc, jazzy) should be used to public docs to github pages.

documentation

context parameters and the parameter views should support optional bindings when applicable.

enhancement

A parameter view which allows for passing of a collection of objects, for example `[Int]`. This should push into another list showing each of the contents, along with a button...

enhancement

While the UI functions as intended, the Xcode / Device console is being spammed with warnings regarding some autolayout conflicts. We should identify if these are able to be resolved...

bug

Pull inspiration from other good open source libraries. - [x] Badges - [ ] Swift version / os version support - [x] Remove TODO (Ensure issues exist for all items)...

documentation
help wanted
good first issue

Exhibition should compile for tvOS and have adequate UI for displaying components. - [ ] Fix tvOS compilation - [ ] Add tvOS matrix to CI test job - [...

bug

The swift package currently compiles for watchOS, but the UI is completely untested. We should add a watch extension target to the Example app, and then test and polish the...

enhancement

The example app currently compiles and runs on macOS, but the UI output by Exhibition is untested. We should test the UI and adjust such that it is a good...

enhancement
good first issue

It could be beneficial to provide some default view for displaying colors. Perhaps this could be done by providing a static exhibit builder: ```swift extension Exhibit { static func colors(name:...

enhancement

We should adjust the codebase to use strings file(s) and appropriate localized string, and setup the project to accept localizations into languages other than english.

enhancement