Skip to content

Avoid name collisions #52

@destructivedata

Description

@destructivedata

The Situation

The default nodes currently have very generic names, e.g. Author. This could (and already has) lead to name collisions if the user defines custom nodes with the same name.

Possible Solution

Rename default nodes so that possible name collisions are more unlikely. A naming scheme like DefaultAuthor or CAGAuthor instead of just Author should work fine.

Additional thoughts

The same problem could occur whit edges.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    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