Giter Site home page Giter Site logo

Comments (4)

jrdouceur avatar jrdouceur commented on June 26, 2024 1

I can't repro this failure. I just ran a simple model through ParseToJson() on the latest preview package (1.0.35-preview-gf7d12847e2) and its output included:

{
  . . .
  "dtmi:test:anInterface;1": {
    . . .
    "contents": {
      "expectedDistance": "dtmi:test:aProperty;1",
      "currentDistance": "dtmi:test:aTelemetry;1",
      "setDistance": "dtmi:test:aCommand;1",
      "proximity": "dtmi:test:aRelationship;1"
    },
    "commands": {
      "setDistance": "dtmi:test:aCommand;1"
    },
    "components": {},
    "properties": {
      "expectedDistance": "dtmi:test:aProperty;1"
    },
    "relationships": {
      "proximity": "dtmi:test:aRelationship;1"
    },
    "telemetries": {
      "currentDistance": "dtmi:test:aTelemetry;1"
    },
    . . .
  },
  . . .
}

from dtdlparser.

rido-min avatar rido-min commented on June 26, 2024

should the new breakout properties reference the concrete interfaces?

from

export interface InterfaceInfo extends EntityInfo {
  EntityKind: 'Interface';
  contents: { [name: string]: string };
  commands: { [name: string]: string };
  components: { [name: string]: string };
  properties: { [name: string]: string };
  relationships: { [name: string]: string };
  telemetries: { [name: string]: string };
  extends: string[];
  extendedBy: string[];
  schemas: string[];
}

to

export interface InterfaceInfo extends EntityInfo {
  EntityKind: 'Interface';
  contents: { [name: string]: ContentInfo };
  commands: { [name: string]: CommandInfo };
  components: { [name: string]: ComponentInfo };
  properties: { [name: string]: PropertyInfo };
  relationships: { [name: string]: RelationshipInfo };
  telemetries: { [name: string]: TelemetryInfo };
  extends: string[];
  extendedBy: string[];
  schemas: string[];
}

from dtdlparser.

jrdouceur avatar jrdouceur commented on June 26, 2024

The DtdlOm.d.ts file describes the JSON returned by ParseToJson(), which does not return a hierarchical structure. The JSON object that is the value of, e.g., "components" maps name strings to DTMI strings, not to ComponentInfo JSON objects. This is the same for the breakout properties as it is/was for the "contents" property.

from dtdlparser.

rido-min avatar rido-min commented on June 26, 2024

got it.

I'm leaving this issue open until the JS sample is updated to reflect those properties (that will require to populate to full objects)

from dtdlparser.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.