-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
Compile time dependencies check #234
Comments
Hi! I already thought of this, but the thing is people can choose to manually call their Composables, at which point it's really impossible to tell at compile time whether there is a missing dependency or the developer is just doing that (calling it manually). I'll keep this open as a possible future enhancement. |
let's say I have a composable with some dependencies.
is there a way to ensure that the dependencies of the above composable are satisfied at compile time like dagger/hilt does instead of doing it at runtime?
this to avoid forgetting to pass the dependency and realise about it once the whole project has been compiled and run.
The text was updated successfully, but these errors were encountered: