Skip to content

Entry in targets.json appears to be missing opposites field, not sure if it's a bug #285

@emberlightstudios

Description

@emberlightstudios
        {
                "has_left_and_right": true,
                "label": "eye-trans-in-out",
                "name": "eye-trans-in-out",
                "opposites": {
                    "negative-left": "l-eye-trans-in",
                    "negative-right": "r-eye-trans-in",
                    "negative-unsided": "",
                    "positive-left": "l-eye-trans-out",
                    "positive-right": "r-eye-trans-out",
                    "positive-unsided": ""
                },
                "targets": [
                    "l-eye-trans-in",
                    "r-eye-trans-out",
                    "r-eye-trans-in",
                    "l-eye-trans-out"
                ]
            },
            {
                "has_left_and_right": true,
                "label": "eye-eyefold-concave-convex",
                "name": "eye-eyefold-concave-convex",
                "targets": [
                    "r-eye-eyefold-concave",
                    "r-eye-eyefold-convex",
                    "l-eye-eyefold-concave",
                    "l-eye-eyefold-convex"
                ]
            }

should the 2nd entry here have the opposites field? seems to me that it should.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions