-
Notifications
You must be signed in to change notification settings - Fork 25
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
Adding Tabs/BottomNav Routing Samples #1267
Adding Tabs/BottomNav Routing Samples #1267
Conversation
src/app/layouts/tabbar/tabbar-sample-3/tabbar-sample-3.component.html
Outdated
Show resolved
Hide resolved
src/app/layouts/tabs/tabs-sample-6/tabs-sample-6.component.html
Outdated
Show resolved
Hide resolved
src/app/layouts/tabbar/tabbar-sample-3/tabbar-sample-3.component.html
Outdated
Show resolved
Hide resolved
src/app/layouts/tabs/tabs-sample-6/tabs-sample-6.component.html
Outdated
Show resolved
Hide resolved
…ub.com/IgniteUI/igniteui-angular-samples into rkolev/tabsBottonNavTabsDefinitionMode
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking into the other samples for Tabs and BottomNav, it seems they are showing more real use scenarios - tabs with contacts or some information about an artist. I think we should reconsider the content presented in the routing samples.
The routing sample now has a new data source and different components are used. |
IgniteUI/igniteui-angular#4297