This repository was archived by the owner on Aug 4, 2020. It is now read-only.
Update quality tags #77
Merged
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
This PR fixes/implements the following bugs/features
update-assetsscript so the prism css isn't being copied since we've changed to a custom theme that is more accessible@webcomponents/custom-elementsto v1.2.4*Note:
The scoring scale for the quality tags has been updated to align with the new data quality algorithm for code.gov. Updated info is below.
The
quality-tagcomponent will determine the corner tag to add (either high, medium, or low) based on thescorevalue passed. The range for these is:See quality_tag.js to view the code for this logic.