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
Our current implementation assumes the consumer is using Xcode project test targets when trying to find the feature files. The defaults don’t work for an SPM test target, you need to remember to pass .module or it won’t find the features. Given the way things are going, it doesn't make sense to have such a default.
A naive solution would involve two changes:
For the Feature() function, we make bundle a required param. For Xcode projects, the consumer would specify Bundle(for: Self.self) and for SPM .module.
GenerateFeature_EXPERIMENTAL also has bundle as a required param. When generating the code, it should preserve the bundle param from its call site in the generated Feature call.
We can also see if there's a cleaner solution that avoids the user having to pass the bundle explicitly.
The text was updated successfully, but these errors were encountered:
Our current implementation assumes the consumer is using Xcode project test targets when trying to find the feature files. The defaults don’t work for an SPM test target, you need to remember to pass
.module
or it won’t find the features. Given the way things are going, it doesn't make sense to have such a default.A naive solution would involve two changes:
Feature()
function, we makebundle
a required param. For Xcode projects, the consumer would specifyBundle(for: Self.self)
and for SPM.module
.GenerateFeature_EXPERIMENTAL
also hasbundle
as a required param. When generating the code, it should preserve thebundle
param from its call site in the generatedFeature
call.We can also see if there's a cleaner solution that avoids the user having to pass the
bundle
explicitly.The text was updated successfully, but these errors were encountered: