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

Mark fixture data as HTML safe #36

Merged
merged 1 commit into from Aug 23, 2017
Merged

Mark fixture data as HTML safe #36

merged 1 commit into from Aug 23, 2017

Conversation

@fofr
Copy link
Contributor

@fofr fofr commented Aug 23, 2017

Allow HTML strings to be written in YAML and rendered in the component guide as examples.

It is preferable to mark our trusted YAML strings as html_safe than to require .html_safe be included within each component. Safe HTML blocks are acceptable arguments to a component.

Allow HTML strings to be written in YAML and rendered in the component
guide as examples.
@nickcolley nickcolley merged commit 739ef94 into master Aug 23, 2017
1 check passed
1 check passed
continuous-integration/jenkins/branch This commit looks good
Details
@nickcolley nickcolley deleted the html-in-fixtures branch Aug 23, 2017
fofr added a commit that referenced this pull request Aug 25, 2017
* Add aXe accessibility testing javascript (PR #33)
* Mark strings in YAML fixtures as HTML safe (PR #36)
* Refactor internal structs to use classes (PR #34)
@fofr fofr mentioned this pull request Aug 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.