Fix the micodata option when set as a direct option of render_crumbs #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Great, thanks' |
andrew
added a commit
that referenced
this pull request
Aug 29, 2013
Fix the micodata option when set as a direct option of render_crumbs
|
I've published this fix as part of v1.8.0 now: https://github.com/zachinglis/crummy/releases/tag/v1.8.0 Thanks again |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If
Crummy.configuration.microdatais set to true, passing in:microdata => falsetorender_crumbswill currently have no effect (due to the||=semantics). This fixes that issues and adds some tests around the boolean options.