vaadin-radio-button

WebJar for vaadin-radio-button

License

License

Categories

Categories

Vaadin User Interface Web Frameworks Github Development Tools Version Controls
GroupId

GroupId

org.webjars.bower
ArtifactId

ArtifactId

github-com-vaadin-vaadin-radio-button
Last Version

Last Version

v1.0.0-alpha8
Release Date

Release Date

Type

Type

jar
Description

Description

vaadin-radio-button
WebJar for vaadin-radio-button
Project URL

Project URL

http://webjars.org
Source Code Management

Source Code Management

https://github.com/vaadin/vaadin-radio-button

Download github-com-vaadin-vaadin-radio-button

How to add to project

<!-- https://jarcasting.com/artifacts/org.webjars.bower/github-com-vaadin-vaadin-radio-button/ -->
<dependency>
    <groupId>org.webjars.bower</groupId>
    <artifactId>github-com-vaadin-vaadin-radio-button</artifactId>
    <version>v1.0.0-alpha8</version>
</dependency>
// https://jarcasting.com/artifacts/org.webjars.bower/github-com-vaadin-vaadin-radio-button/
implementation 'org.webjars.bower:github-com-vaadin-vaadin-radio-button:v1.0.0-alpha8'
// https://jarcasting.com/artifacts/org.webjars.bower/github-com-vaadin-vaadin-radio-button/
implementation ("org.webjars.bower:github-com-vaadin-vaadin-radio-button:v1.0.0-alpha8")
'org.webjars.bower:github-com-vaadin-vaadin-radio-button:jar:v1.0.0-alpha8'
<dependency org="org.webjars.bower" name="github-com-vaadin-vaadin-radio-button" rev="v1.0.0-alpha8">
  <artifact name="github-com-vaadin-vaadin-radio-button" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.webjars.bower', module='github-com-vaadin-vaadin-radio-button', version='v1.0.0-alpha8')
)
libraryDependencies += "org.webjars.bower" % "github-com-vaadin-vaadin-radio-button" % "v1.0.0-alpha8"
[org.webjars.bower/github-com-vaadin-vaadin-radio-button "v1.0.0-alpha8"]

Dependencies

compile (3)

Group / Artifact Type Version
org.webjars.bower : polymer jar [2.0.0,3)
org.webjars.bower : vaadin-control-state-mixin jar [1.1.0,2)
org.webjars.bower : vaadin-themable-mixin jar [1.1.0,2)

Project Modules

There are no modules declared in this project.

<vaadin-radio-button>

<vaadin-radio-button> is a Web Component providing an accessible and customizable radio button, part of the Vaadin components.

Live Demo | API documentation

npm version Published on webcomponents.org Build Status Coverage Status Gitter Published on Vaadin  Directory Stars on vaadin.com/directory

⚠️ This is a pre-release version built with LitElement, part of the next generation of Vaadin web components.

Looking for Vaadin 14 compatible version? Please see the following branches:

<vaadin-radio-group name="radio-group" value="bar">
  <vaadin-radio-button value="foo">Foo</vaadin-radio-button>
  <vaadin-radio-button value="bar">Bar</vaadin-radio-button>
  <vaadin-radio-button value="baz">Baz</vaadin-radio-button>
</vaadin-radio-group>

Screenshot of vaadin-radio-group

Installation

Install vaadin-radio-button:

npm i @vaadin/vaadin-radio-button --save

Once installed, import it in your application:

import '@vaadin/vaadin-radio-button/vaadin-radio-button.js';

Getting started

Vaadin components use the Lumo theme by default.

To use the Material theme, import the correspondent file from the theme/material folder.

Entry points

  • The components with the Lumo theme:

    theme/lumo/vaadin-radio-button.js theme/lumo/vaadin-radio-group.js

  • The components with the Material theme:

    theme/material/vaadin-radio-button.js theme/material/vaadin-radio-group.js

  • Alias for theme/lumo/vaadin-radio-button.js theme/lumo/vaadin-radio-group.js:

    vaadin-radio-button.js vaadin-radio-group.js

Running demos and API docs in a browser

  1. Fork the vaadin-radio-button repository and clone it locally.

  2. Make sure you have npm installed.

  3. When in the vaadin-radio-button directory, run npm install to install dependencies.

  4. Run npm start, browser will automatically open the component API documentation.

Running tests from the command line

  • When in the vaadin-radio-button directory, run npm test

  • To debug tests in the browser, run npm run test:debug

Following the coding style

We are using ESLint for linting TypeScript code. You can check if your code is following our standards by running npm run lint, which will automatically lint all .ts files.

Big Thanks

Cross-browser Testing Platform and Open Source <3 Provided by Sauce Labs.

Contributing

To contribute to the component, please read the guideline first.

License

Apache License 2.0

Vaadin collects development time usage statistics to improve this product. For details and to opt-out, see https://github.com/vaadin/vaadin-usage-statistics.

org.webjars.bower

Vaadin

An open platform for building modern web apps for Java back ends

Versions

Version
v1.0.0-alpha8
v1.0.0-alpha4