Replies: 4 comments · 5 replies
-
|
Hi @xaverlutz, are you sure this is a TCA-specific issue? It seems more likely that it's a Swift/DocC bug where docs fail to build anytime a macro is involved that generates inner types. Can you try reproducing the problem in a fresh project without TCA involved, and if you succeed then I think this needs to be filed with Apple. I'm not sure there is much we can do to fix this. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @xaverlutz, I'm going to move this to a discussion since I'm not sure it's actually a TCA-specific issue. Sounds like a general Swift/macro issue. Please let us know if you uncover anything new. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mbrandonw, Based on your suggestion I've created a test project (here) with a macro package that just adds an inner type and an additional macro that adds a type to the inner type. As soon as the TCA is introduced with the Of course this still doesn't rule out that it is an issue with Swift/DocC, so I hope you might have a lead on what we should might try next. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @rszczepanski, I would continue adding more features to your And I just doubt there is anything that we are doing in TCA that should be breaking DocC. As a matter of principle that just shouldn't be possible, and so it seems more likely that this is just a bug with macros and DocC. By the way, the repro of this problem is far simpler than using @Reducer
struct TestStruct {}I think this makes it even more clear that this is a DocC issue, and so it should be possible to get a minimal reproducible project to share with Apple. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Are there any updates on resolving this issue? The problem still persists and DocC is still broken. It's really upsetting. Has anyone found a solution by any chance? |
Beta Was this translation helpful? Give feedback.
-
|
It appears that Apple is tracking some bugs internally: swiftlang/swift-docc#849 I think the best bet is to continue to repro using small examples that can be filed with Apple. |
Beta Was this translation helpful? Give feedback.
-
|
Hi!! Still having the same issue with Xcode 16. @stensmir did you manage to get solution? |
Beta Was this translation helpful? Give feedback.
-
|
Well the only workaround right now seems to be: expand the macro and copy the generated Action/State enums in your codebase |
Beta Was this translation helpful? Give feedback.
-
|
It seems like Xcode 16.3 fixes this issue. |
Beta Was this translation helpful? Give feedback.
-
Description
Hi,
after migrating our app to 1.8 and adjusting the
Destinationenums, we are unable to build the documentation using either Xcode or the xcodebuild command. The error can be seen in the image below.The error is from my dummy project, as I wanted to verify if we migrated something wrong. The project can be accessed at this link.
Checklist
mainbranch of this package.Expected behavior
No response
Actual behavior
No response
Steps to reproduce
The Composable Architecture version information
1.8 & 1.9.2
Destination operating system
iOS 17.0
Xcode version information
Version 15.3 (15E204a)
Swift Compiler version information
Beta Was this translation helpful? Give feedback.
All reactions