JarCasting
JarCasting JarCasting

vaadin-text-field

WebJar for vaadin-text-field

License

License
Categories

Categories

Vaadin User Interface Web Frameworks
GroupId

GroupId

org.webjars.bowergithub.heruan
ArtifactId

ArtifactId

vaadin-text-field
Last Version

Last Version

2.4.2-axians1
Release Date

Release Date
Type

Type

jar
Description

Description

vaadin-text-field
WebJar for vaadin-text-field
Project URL

Project URL

http://webjars.org
Source Code Management

Source Code Management

https://github.com/heruan/vaadin-text-field

Download vaadin-text-field

Filename Size
vaadin-text-field-2.4.2-axians1.pom
vaadin-text-field-2.4.2-axians1.jar 260 KB
vaadin-text-field-2.4.2-axians1-sources.jar 22 bytes
vaadin-text-field-2.4.2-axians1-javadoc.jar 22 bytes
Browse

How to add to project

<!-- https://jarcasting.com/artifacts/org.webjars.bowergithub.heruan/vaadin-text-field/ -->
<dependency>
    <groupId>org.webjars.bowergithub.heruan</groupId>
    <artifactId>vaadin-text-field</artifactId>
    <version>2.4.2-axians1</version>
</dependency>
// https://jarcasting.com/artifacts/org.webjars.bowergithub.heruan/vaadin-text-field/
implementation 'org.webjars.bowergithub.heruan:vaadin-text-field:2.4.2-axians1'
// https://jarcasting.com/artifacts/org.webjars.bowergithub.heruan/vaadin-text-field/
implementation ("org.webjars.bowergithub.heruan:vaadin-text-field:2.4.2-axians1")
'org.webjars.bowergithub.heruan:vaadin-text-field:jar:2.4.2-axians1'
<dependency org="org.webjars.bowergithub.heruan" name="vaadin-text-field" rev="2.4.2-axians1">
  <artifact name="vaadin-text-field" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.webjars.bowergithub.heruan', module='vaadin-text-field', version='2.4.2-axians1')
)
libraryDependencies += "org.webjars.bowergithub.heruan" % "vaadin-text-field" % "2.4.2-axians1"
[org.webjars.bowergithub.heruan/vaadin-text-field "2.4.2-axians1"]

Dependencies

compile (6)

Group / Artifact Type Version
org.webjars.bowergithub.vaadin : vaadin-themable-mixin jar [1.2.1,2)
org.webjars.bowergithub.polymer : polymer jar [2.0.0,3)
org.webjars.bowergithub.vaadin : vaadin-material-styles jar [1.2.0,2)
org.webjars.bowergithub.vaadin : vaadin-element-mixin jar [2.0.0,3)
org.webjars.bowergithub.vaadin : vaadin-control-state-mixin jar [2.1.1,3)
org.webjars.bowergithub.vaadin : vaadin-lumo-styles jar [1.2.0,2)

Project Modules

There are no modules declared in this project.

Bower version Published on webcomponents.org Build Status Gitter

<vaadin-text-field>

Live Demo ↗ | API documentation ↗

<vaadin-text-field> is a themable Polymer 2 element providing input controls in forms, part of the Vaadin Core Elements.

<vaadin-text-field label="Username"></vaadin-text-field>
<vaadin-password-field label="Password"></vaadin-password-field>
<vaadin-text-area label="Description"></vaadin-text-area>

Screenshot of vaadin-text-field

Getting Started

Vaadin Elements use the Lumo theme by default.

The file structure for Vaadin Elements

  • src/vaadin-text-field.html

  • src/vaadin-text-area.html

  • src/vaadin-password-field.html

    Unstyled elements.

  • theme/lumo/vaadin-text-field.html

  • theme/lumo/vaadin-text-area.html

  • theme/lumo/vaadin-password-field.html

    Elements with Lumo theme.

  • vaadin-text-field.html

  • vaadin-text-area.html

  • vaadin-password-field.html

    Aliases for theme/lumo/vaadin-text-field.html theme/lumo/vaadin-text-area.html theme/lumo/vaadin-password-field.html

Running demos and tests in browser

  1. Fork the vaadin-text-field repository and clone it locally.

  2. Make sure you have npm installed.

  3. When in the vaadin-text-field directory, run npm install and then bower install to install dependencies.

  4. Run polymer serve --open, browser will automatically open the component API documentation.

  5. You can also open demo or in-browser tests by adding demo or test to the URL, for example:

Running tests from the command line

  1. When in the vaadin-text-field directory, run polymer test

Following the coding style

We are using ESLint for linting JavaScript code. You can check if your code is following our standards by running gulp lint, which will automatically lint all .js files as well as JavaScript snippets inside .html files.

Creating a pull request

  • Make sure your code is compliant with our code linters: gulp lint
  • Check that tests are passing: polymer test
  • Submit a pull request with detailed title and description
  • Wait for response from one of Vaadin Elements team members

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.

Versions

Version
2.4.2-axians1
2.0.1-label-suffix
2.0.0-beta4-label-suffix