You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.
A project I am working on correlates our Storyboard file's names with the UIViewController subclass that is it's initial view controller. The result is a Storyboards.*struct that conflicts in naming with the view controller type itself:
I appreciate the brevity of the struct's name and appending something like "File" clutters that. On the other hand it is more explicit: these are mappings to files as much as we'd love to abstract them away.
The text was updated successfully, but these errors were encountered:
There is no compile issue?
because there is Storyboards.ExampleViewController vs ExampleViewController
The only things we can do is apply naming rules according to some options, like adding a postfix (like Storyboard) or remove some part like ViewController
There is a compilation issue because of that conflict.
I would expect the resulting code to be an expected, consistent output, ie: not to do a different naming convention for some VCs because they conflict but not for others because they don't. Applying a naming rule or removing parts may decrease the likelihood of a conflict but it will still be a possibility.
Other possibility, with Swift we can specify the specific ExampleViewcontroller we are referencing if we know the project's module name:
A project I am working on correlates our
Storyboard
file's names with theUIViewController
subclass that is it's initial view controller. The result is aStoryboards.*
struct
that conflicts in naming with the view controller type itself:I appreciate the brevity of the struct's name and appending something like "File" clutters that. On the other hand it is more explicit: these are mappings to files as much as we'd love to abstract them away.
The text was updated successfully, but these errors were encountered: