Skip to content

DOC-1638 Add multiple edge section#352

Open
priyankagunaki-cloud wants to merge 1 commit into
4.3from
DOC-1638-add-info-multiple-edge
Open

DOC-1638 Add multiple edge section#352
priyankagunaki-cloud wants to merge 1 commit into
4.3from
DOC-1638-add-info-multiple-edge

Conversation

@priyankagunaki-cloud

Copy link
Copy Markdown
Contributor

No description provided.

CREATE DIRECTED EDGE Member_Of (FROM Person, TO Org | FROM Org, TO Org, joined DATETIME)
----

=== Multi-edges

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@priyankagunaki-cloud The ticket said to add a section, so you did. Now consider the resulting page.
You have a new Heading 3 section about Multi-edges, which describes why they are useful and then says the way to create them is with a Discriminator. There is an example, which was copied from the Discriminator section. This is immediately followed by a Heading 3 section (same level) which describes Discriminators. It again shows the same example.

Does this not seem redundant to you?

This is why I say do not blindly follow tickets. A ticket is trying to describe a problem or need. Understand the need, then figure out the best way to address it. The person who wrote the ticket may not have put in the time to understand the full context, or they may not be the best writer or explainer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants