npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

prendus-question-elements

v0.15.4

Published

Fully embeddable custom HTML elements for Prendus questions.

Downloads

31

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

lastmjslastmjs

Keywords

Readme

Prendus Question Elements

CircleCI npm version dependency Status devDependency Status Published on webcomponents.org

Question demo

Fully embeddable custom HTML elements for questions made with AssessML. Use these elements in any web platform project, including Web Components, Polymer, SkateJS, React, Vue.js, Angular, Ember.js, and Vanilla.

Demos

Playground with blank editor

Multiple choice

Basic demo

Advanced demo

Multiple select

Basic demo

Advanced demo

Fill in the blank

Basic demo

Advanced demo

Essay

Basic demo

Advanced demo

Code

Basic demo

Advanced demo

Variables

Basic demo

Advanced demo

Math symbols

Basic demo

Advanced demo

Images

Basic demo

Advanced demo

Graphs

Basic demo

Advanced demo

Solution

Basic demo

Advanced demo

Installation

To use in your own project:

npm install prendus-question-elements

# Eventually the bower commands below will disappear, but until we can fully support npm, sorry

bower install polymer --save
bower install paper-tabs --save
bower install juicy-ace-editor --save
bower install iron-pages --save
bower install wysiwyg-e --save
bower install paper-toast --save
bower install paper-dialog --save
bower install paper-input --save
bower install paper-button --save
bower install iron-icon --save
bower install paper-tooltip --save

To work on locally:

git clone https://github.com/Prendus/prendus-question-elements
cd prendus-question-elements
npm install
npm run test-window

Use

The elements are written in TypeScript, and there is no build process. You will have to implement your own build process to consume them. We use Zwitterion.

Import the Web Components polyfill for cross-browser compatibility:

...
<head>
  <script src="[path to bower_components]/webcomponentsjs/webcomponents-lite.js"></script>
</head>
...

Import the element that you would like to use:

<link rel="import" href="[path to node_modules]/prendus-question-elements/prendus-view-question.html">
<link rel="import" href="[path to node_modules]/prendus-question-elements/prendus-edit-question.html">

Then use the element wherever you would like:

<prendus-view-question question-id="cj4os7mld6kq4017073x00cjt"></prendus-view-question>
<prendus-edit-question question-id="cj4os7mld6kq4017073x00cjt"></prendus-edit-question>

API

prendus-view-question

Properties

questionId: string

The Prendus question ID for this question. Providing this property will automatically load the question from the Prendus database.

question: Question

A question object can be used to provide the text and code of a question directly instead of loading it from the Prendus database. Any Question passed in must have the following interface:

interface Question {
  readonly text: string;
  readonly code: string;
}

prendus-edit-question

Properties

questionId: string

The Prendus question ID for this question. Providing this property will automatically load the question from the Prendus database.

question: string

A question object can be used to provide the text and code of a question directly instead of loading it from the Prendus database. Any Question passed in must have the following interface:

interface Question {
  text: string;
  code: string;
}
user: User

A Prendus user. This user (along with the userToken) is necessary to enforce many of the permissions on the questions. Any user passed in must have the following interface:

interface User {
  id: string;
}
userToken: string

The Graphcool JSON Web Token associated with a user. This token (along with the user) is necessary to enforce many of the permissions on the questions.

noSave: boolean

Whether or not to execute API calls to save the question to the database on changes to the question text or code.