Directory

← Back

granite-prism-marked-element

An element extending marked-element with encapsulated prism-element and prism-theme-default to be more easily used in non-polymer apps

Author

Rating

Popularity

<100

[ This description is mirrored from README.md at github.com/LostInBrittany/granite-prism-marked-element on 2019-05-22 ]

Published on webcomponents.org

granite-prism-marked-element

Based on Polymer 2.x

An element extending marked-element with encapsulated prism-element and prism-theme-default to be more easily used in non-polymer apps

See https://www.webcomponents.org/element/PolymerElements/marked-element for more info

Usage example

<granite-prism-marked-element >
    <script type="text/markdown">
        # Does it works?

        I am not sure! 

        Let's test

        ```html
        <div>There is no div here</div>
        <i>
            console.log('And no log');
        </i>
        ```

        **Yes it works!**
    </script>
</granite-prism-marked-element>

Install the Polymer-CLI

First, make sure you have the Polymer CLI installed. Then run polymer serve to serve your element locally.

Viewing Your Element

$ polymer serve

Running Tests

$ polymer test

Your application is already set up to be tested via web-component-tester. Run polymer test to run your application's test suite locally.

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -m 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

License

MIT

Compatibility

(Loading compatibility data...)

Was this helpful? Need more help?
Leave a comment or a question below. You can also join the chat on Discord or ask questions on StackOverflow.

Version

Dependencies

Polymer/polymer#^2.0.0

  • PolymerElements/prism-element#^2.0.1
  • PolymerElements/marked-element#^2.4.0
Released
2018-03-01
Maturity
IMPORTED
License
Other

Compatibility

Framework
Polymer 2.0+
Browser
Browser Independent

granite-prism-marked-element - Vaadin Add-on Directory

An element extending marked-element with encapsulated prism-element and prism-theme-default to be more easily used in non-polymer apps granite-prism-marked-element - Vaadin Add-on Directory
**[ This description is mirrored from README.md at [github.com/LostInBrittany/granite-prism-marked-element](https://github.com//LostInBrittany/granite-prism-marked-element/blob/1.1.0/README.md) on 2019-05-22 ]** [![Published on webcomponents.org](https://img.shields.io/badge/webcomponents.org-published-blue.svg)](https://www.webcomponents.org/element/LostInBrittany/granite-prism-marked-element) # granite-prism-marked-element > Based on Polymer 2.x An element extending marked-element with encapsulated prism-element and prism-theme-default to be more easily used in non-polymer apps See https://www.webcomponents.org/element/PolymerElements/marked-element for more info ## Usage example ```html ``` ## Install the Polymer-CLI First, make sure you have the [Polymer CLI](https://www.npmjs.com/package/polymer-cli) installed. Then run `polymer serve` to serve your element locally. ## Viewing Your Element ``` $ polymer serve ``` ## Running Tests ``` $ polymer test ``` Your application is already set up to be tested via [web-component-tester](https://github.com/Polymer/web-component-tester). Run `polymer test` to run your application's test suite locally. ## Contributing 1. Fork it! 2. Create your feature branch: `git checkout -b my-new-feature` 3. Commit your changes: `git commit -m 'Add some feature'` 4. Push to the branch: `git push origin my-new-feature` 5. Submit a pull request :D ## License [MIT](https://opensource.org/licenses/mit)
Online