Skip to content

refactor(admob): create a separate nav graph for the java sample #1250

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

Merged
merged 1 commit into from
Jan 22, 2021

Conversation

thatfiredev
Copy link
Member

I noticed I made a mistake when I sent #1247 : I only added the Kotlin Fragments to the navigation graph, which caused the java ones to never be used.

As a solution (in this PR), I've created a separate nav graph file for the java fragments (nav_graph_java.xml) and the graphs are now set programmatically (instead of setting it in the XML layout).

@samtstern
Copy link
Contributor

@rosariopfernandes good catch! By the middle of 2021 we should be able to go Kotlin-only on these samples. I'm waiting for some internal Kotlin adoption charts to hit certain thresholds and then we can get some heavy rm -rf java action going :-)

@samtstern samtstern added this to the jetpack milestone Jan 22, 2021
@samtstern samtstern merged commit 3ff015b into firebase:master Jan 22, 2021
@thatfiredev
Copy link
Member Author

@samtstern That's some great news :) Can't wait for it

@thatfiredev thatfiredev deleted the rpf-admob-add-java-nav-graph branch January 22, 2021 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants