-
Notifications
You must be signed in to change notification settings - Fork 35
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
[Question]: I think it's better to move the samples to root project? #573
Comments
Yea, I think that should be fine. Originally there were some problems with Compose in the same class path, but that has been fixed a while ago. |
Handling this currently, unsure if this as easy as it sounds. Each sample has their own modules & settings, which makes it hard to include them all without a lot of boilerplate. Looking at the KotlinX dependencies, most of them have samples with their own gradle project. |
@MohamedRejeb any idea on this? |
I think that the library needs convention plugins, it will make this much easier. I can work on this if it makes sense to you. |
If we mean the same thing, we already have some methods to make the configuration easier: |
Probably a bit less if the Gradle files are cached, but its still ~25-30min. |
We can conditionally exclude samples from build when needed. Something like this should work: if (System.getProperty("LibrariesOnly") != "true") {
include(":sample:kmp")
} ./gradlew -PLibrariesOnly=true build |
General info
What is your question?
HI,
I think it's better to move samples to the root project, it's easier for testing and debugging. You can directly run the sample with the latest changes without the need to publish the library. Also, when you clone the project, the IDE will only recognize the root project and you need to open the samples as separate projects.
Relevant log output (optional)
No response
The text was updated successfully, but these errors were encountered: