Stop arguing about code style and let automation handle it
Imagine this: You're reviewing a pull request, and half the comments are about formatting—missing newlines, trailing spaces, inconsistent indentation. Sound familiar?
Stop arguing about code style and let automation handle it
Imagine this: You're reviewing a pull request, and half the comments are about formatting—missing newlines, trailing spaces, inconsistent indentation. Sound familiar?
<style name="Theme.App.Starting" parent="Theme.SplashScreen"> | |
// Set the splash screen background, animated icon, and animation duration. | |
<item name="windowSplashScreenBackground">@color/purple_700</item> | |
// Use windowSplashScreenAnimatedIcon to add either a drawable or an | |
// animated drawable. One of these is required. | |
<item name="windowSplashScreenAnimatedIcon">@drawable/ic_splash</item> | |
<item name="windowSplashScreenAnimationDuration">500</item> # Required for | |
# animated icons | |
<item name="android:windowSplashScreenIconBackgroundColor" tools:targetApi="31">@color/teal_700</item> |