This repository has been archived by the owner on Oct 9, 2024. It is now read-only.
Allow ember-prism to be used by other addons #13
Merged
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.
This change allows addons to make use of
ember-prism
in their own components (with a bit of elbow grease from the author). It contains small refactorings to expose two functions,installPrismBowerPackage
andimportPrismSources
, to allow consuming addons to pull Prism into their host applications. This follows a similar form-factor to the solution used by ember-tether.I pulled the definition of those two functions off of their owning objects to reinforce for the authors of any future changes that they're now "public", but can move them back inline if you'd prefer.
The change as a whole just amounted to some refactoring and documentation. Apps using
ember-prism
today should see no difference.Note: one acceptance test (
Acceptance | CodeBlock: has
line-numbersplugin
) is failing, but that also seems to be the case on master.