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

tplate-java

v0.1.2

Published

Renders Java classes based on JSON schemas

Downloads

2

Readme

tplate-java

npm version

What ...?

tplate-java is a set of tplate segments tailored to generating Java code. Note that it is not the responsibility of tplate-java to generate perfect (or even necessarily compilable) code. It is, however, meant to ease your Java code generation.

Installation

npm install tplate tplate-java --save

Usage

See the examples folder for examples.

Also, please see the unit tests for the expected behavior of this library.

The Very Basics

import { createTemplate } from 'tplate';
import { fileSegment } from 'tplate-java';

const { t } = createTemplate();
const output = t(classSegment({
  inPackage: 'com.example.first',
  javaClass: { name: 'Unicorn' }
}));
// =>
// package com.example.first;
// 
// public class Unicorn {
// }

API

fileSegment(fileSpec): String

Outputs a typical Java class/interface/enum file. The fileSpec is as follows (note that you may only define one of javaClass, javaEnum or javaInterface):

{
  inPackage: 'com.example',
  imports: [<importSegment>, ...],
  javaClass: <classSegment>,
  javaEnum: <enumSegment>,
  javaInterface: <interfaceSegment>
}

classSegment(classSpec): String

Outputs a Java class, but without the package definition and import statements. The classSpec is as follows:

{
  name: 'YourClass',
  extendsClass: 'YourAbstractClass',
  genericTypes: [<genericTypeSegment>, ...],
  accessModifier: 'public',
  scope: 'instance',
  interfaces: [<interfaceImplementationSegment>, ...],
  annotations: [<annotationSegment>, ...],
  fields: [<fieldSegment>, ...],
  constructors: [<constructorSegment>, ...],
  methods: [<methodSegment>, ...],
  innerClasses: [<classSegment>, ...]
}

interfaceSegment(interfaceSpec): String

Outputs a Java interface, but without the package definition and import statements. The interfaceSpec is as follows:

{
  name: 'YourInterface',
  extendsInterfaces: [<interfaceImplementationSegment>, ...],
  genericTypes: [<genericTypeSegment>, ...],
  accessModifier: 'public',
  scope: 'instance',
  annotations: [<annotationSegment>, ...],
  methods: [<methodSegment>, ...]
}

enumSegment(enumSpec): String

Outputs a Java enumeration, but without the package definition and import statements. The enumSpec is as follows:

{
  name: 'YourEnum',
  accessModifier: 'public',
  scope: 'instance',
  interfaces: [<interfaceImplementationSegment>, ...],
  annotations: [<annotationSegment>, ...],
  fields: [<fieldSegment>, ...],
  constants: [<constantSegment>, ...],
  constructors = [<constructorSegment>, ...],
  methods = [<methodSegment>, ...]
}

applyMiddleware(...middleware): segments

Applies middleware to your segments. Each middleware will be called before a spec is sent to the segments. This allows each middleware to transform or override the spec before passing it to the next middleware and, ultimately, to the segments.

tplate-java comes with two built-in middleware. (You are of course free to implement your own!) These are:

  • importCollectorMiddleware (intended for use with fileSegment): Collects all (nested) type properties in the spec, and populates the imports property in the fileSpec accordingly. This may be helpful, because you don't have to bother with the imports yourself. This is, however, only partially true, because it does not consider the usage of external classes, enums or interfaces that are in method bodies, for instance. Only type properties are taken into consideration.
  • typePackageRemoverMiddleware (intended for use with fileSegment): Removes all package paths from all (nested) type properties in the spec. For instance, it will transform java.util.List<String> to List<String>. Intended for use with the importCollectorMiddleware (see above).

Note: It is important that you apply the importCollectorMiddleware before the typePackageRemoverMiddleware.

import { createTemplate } from 'tplate';
import { applyMiddleware } from 'tplate-java';
import { importCollectorMiddleware } from
  'tplate-java/dist/middleware/importCollectorMiddleware';
import { typePackageRemoverMiddleware } from
  'tplate-java/dist/middleware/typePackageRemoverMiddleware';
  
const { t } = createTemplate();
const { fileSegment } = applyMiddleware(
  importCollectorMiddleware,
  typePackageRemoverMiddleware
);

t(fileSegment(/* ... */));

See the unit test for a concrete example.

License

MIT © Arild Tvergrov