Skip to content

feat(api): Add proper handling of Project Properties API vs JSON differences #29

@rlabbeptc

Description

@rlabbeptc

The API design is slightly different than the JSON encoded project file design for project properties. While the API returns the specific properties from config/v1/project/, the JSON serialization of the project file will store the properties in the "client_interfaces" key as an array of the "interfaces" and their associated properties.

Right now, if the LoadProject method is executed to load the full project (config/v1/project?content=serialize) the client_interfaces are received as dynamic properties. If the LoadProject is executed to just access the project properties, each project property will be a unique dynamic property.

LoadProject without full load or a pre v6.17/1.10 version of Kepware:

Image

LoadProject with full load:

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions