Skip to content

Rename DestinationLabel on BottomNavigationBar - #7281

Merged
Hixie merged 4 commits into
flutter:masterfrom
goposse:pp-rename-destinationlabel
Dec 18, 2016
Merged

Hixie merged 4 commits into
flutter:masterfrom
goposse:pp-rename-destinationlabel

Conversation

@lukef

@lukef lukef commented Dec 16, 2016

Copy link
Copy Markdown
Contributor
  • Renamed DestinationLabel to BottomNavigationBarItem
  • Renamed BottomNavigationBarItem.labels to BottomNavigationBarItem.items
  • Adjusted comments

}

/// An interactive destination label within [BottomNavigationBar] with an icon
/// An interactive item within [BottomNavigationBar] with an icon

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I'd leave this as "destination label" so it matches the spec. In general we prefer the docs to use terms that don't match the class names since matching the class names doesn't help anyone. :-)

/// labels laid out on top of a piece of material. It provies quick navigation
/// between top-level views of an app and is typically used on mobile. For
/// larger screens, side navigation may be a better fit.
/// The bottom navigation bar consists of multiple item in the form of

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

grammar

/// between top-level views of an app and is typically used on mobile. For
/// larger screens, side navigation may be a better fit.
/// The bottom navigation bar consists of multiple item in the form of
/// labels and/or icons laid out on top of a piece of material. It provides

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

prefer "labels, icons, or both"

/// The bottom navigation bar consists of multiple item in the form of
/// labels and/or icons laid out on top of a piece of material. It provides
/// quick navigation between top-level views of an app and is typically used
/// on mobile. For larger screens, side navigation may be a better fit.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on mobile what?

@lukef

lukef commented Dec 16, 2016

Copy link
Copy Markdown
Contributor Author

I adjusted the comments based on your feedback. I removed the "primarily used on mobile" as it seems to have been pulled from the material spec directly and its the only real use case right now. I left in a note about larger format devices/screens (it's also in the spec) as it could be useful design advice. Let me know if you want that pulled.

/// larger screens, side navigation may be a better fit.
/// The bottom navigation bar consists of multiple items in the form of
/// labels, icons, or both laid out on top of a piece of material. It provides
/// quick navigation between the top-level views of an app. Note: for larger screens,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/// between top-level views of an app and is typically used on mobile. For
/// larger screens, side navigation may be a better fit.
/// The bottom navigation bar consists of multiple items in the form of
/// labels, icons, or both laid out on top of a piece of material. It provides

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

grammar nit: i'd put a comma after "both" to make it clear that the next part doesn't only apply to the "both" option.

@Hixie

Hixie commented Dec 16, 2016

Copy link
Copy Markdown
Contributor

LGTM

@lukef

lukef commented Dec 16, 2016 •

Copy link
Copy Markdown
Contributor Author

I'll be doing another PR later for a few other things so I can incorporate the feedback at that time.

@Hixie

Hixie commented Dec 16, 2016

Copy link
Copy Markdown
Contributor

Yes for the changes, but it's fine if you do them in the coming days instead of right away.

@lukef

lukef commented Dec 17, 2016

Copy link
Copy Markdown
Contributor Author

Done

@Hixie

Hixie commented Dec 17, 2016

Copy link
Copy Markdown
Contributor

+1 thanks!

@sethladd

Copy link
Copy Markdown
Contributor

Thanks @lukef !

@Hixie is your LGTM sufficient to merge this?

@sethladd

Copy link
Copy Markdown
Contributor

@lukef would you like to add yourself to our AUTHORS file? https://github.com/flutter/flutter/blob/master/AUTHORS

@lukef

lukef commented Dec 17, 2016

Copy link
Copy Markdown
Contributor Author

Added myself. Thanks! 👍

@Hixie

Hixie commented Dec 18, 2016

Copy link
Copy Markdown
Contributor

Merged. FYI @abarth for the API change. We should make sure we've not left any DestinationLabels anywhere.

Luke, would you mind e-mailing flutter-dev to let them know about the API change? Thanks!

@Hixie
Hixie merged commit 1b9939a into flutter:master Dec 18, 2016
@Hixie

Hixie commented Dec 18, 2016

Copy link
Copy Markdown
Contributor

And thanks for the contribution! Much appreciated!

@lukef
lukef deleted the pp-rename-destinationlabel branch December 19, 2016 22:22
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Aug 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants