Skip to content

Resource naming convention #213

@shivamvedant

Description

@shivamvedant

If the model has a resource going in and out of a location, the code can bypass all the processes in the location and directly send it through the outgoing transport.

To temporarily fix this, I renamed all the resources (with a tag for source location) and transport objects (with a tag for source and sink locations)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions