Skip to content
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

Removed automatic Crumb Trail truncation #112

Merged
merged 18 commits into from
Jan 17, 2017
Merged

Removed automatic Crumb Trail truncation #112

merged 18 commits into from
Jan 17, 2017

Conversation

grahammendick
Copy link
Owner

Originally, if the Crumb Trail didn’t truncate at repeated States then back navigation increased, rather than decreased, the Crumb Trail. But back navigation no longer relies on Crumb Trail truncation, so it’s safe to remove.

If it wasn’t removed then, with the introduction of Navigation React Native, all States would need a custom truncateCrumbTrail function that removes it.

No truncation is the better default.
Repeated state truncation was necessary when back navigation relied on
it. But back navigation truncation doesn’t use truncateCrumbTrail
anymore.
Also, with react native navigation, the crumb trail is more relevant.
Don’t want to override truncateCrumbTrail on every state just to remove
the repeated State truncation rule.
These tests now match the default truncateCrumbTrail implementation.
Need new tests for custom truncation
Custom Trail tests now the same as With Trail tests
@grahammendick grahammendick merged commit 39c97c2 into master Jan 17, 2017
@grahammendick grahammendick deleted the untruncate branch January 17, 2017 19:12
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.

1 participant