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

odata-v4-schema-extract

v1.0.0

Published

> odata codegen tool

Downloads

67

Readme

odata-v4-schema-extract

odata codegen tool

Generate json/ts/js from Common Schema Definition Language (CSDL) v4

http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part3-csdl.html

Install

yarn add odata-v4-schema-extract

Usage

$ odata-v4-schema-extract [options] <url>

Options:

  -h, --help               Show this message
  -j, --json               Output the intermediary json format

  -e NAME, --entity=NAME   Entity to extract
  -i FILE, --input=FILE    Input file to read from
  -n NAME, --name=NAME     Override entity name
  -o FILE, --output=FILE   Path to write to
  -t TMPL, --template=TMPL Lodash compatible template

Examples:

  - Write json schema to std output.

    $ odata-v4-schema-extract --json -i ./metadata.xml

  - Generate code with a custom template.

    $ odata-v4-schema-extract -i ./metadata.xml -o ./Entity.js -t ./template.lodash.js

  - Generate code and pipe prettier.

    $ odata-v4-schema-extract -i ./metadata.xml \
      | prettier --stdin-filepath ./Entity.js \
      > ./Entity.js

  - Read from std input.

    $ curl https://odata.api/$metadata | odata-v4-schema-extract -n MyEntity -o ./Entity.js

Custom output

You can override the codegen template with the -t option.

// Default template (when no `-t` option is set)
import * as csdl from "odata-v4-schema/csdl";

<% entities.map(({ name, modelName, properties }) => { %>
const <%- name %> = csdl.Entity("<%- modelName %>", <%- getCSDLSchema(properties, "csdl") %>);
<% }) %>

<% if (entities.length === 1) { %>
export default <%- model[0].name %>;
<% } else { %>
export { <%- entities.map(({name})=>name).join(", ") %> };
<% } %>

Programatic usage

import { convertStream, buildTemplate } from 'odata-v4-schema-extract'
import got from 'got'

import fs from 'node:fs/promises'
import path from 'node:path'

const template = './scripts/template.lodash.js'

const entities = await convertStream(got.stream(`${process.env.API_PATH}/$metadata`, {
  headers: {
    authorization: `Bearer ${process.env.API_TOKEN}`
  }
}))

await fs.writeFile('./src/models/ProductItem.js', await buildTemplate(entities, {
  entity: 'Products',
  name: 'ProductItem'
  template
}))

await fs.writeFile('./src/models/Customer.js', await buildTemplate(entities, {
  entity: 'Users',
  name: 'Customer'
  template
}))