Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Arrow for Diagram Component #6863

Open
wants to merge 16 commits into
base: master
Choose a base branch
from

Conversation

g4rry420
Copy link
Contributor

@g4rry420 g4rry420 commented Jul 5, 2023

What does this PR do?

Where should the reviewer start?

Diagram.js

What testing has been done on this PR?

Currently, only manually tested using Arrow.js and Animated.js files

How should this be manually tested?

  • Arrow.js and Animated.js files

Do Jest tests follow these best practices?

  • screen is used for querying.
  • The correct query is used. (Refer to this list of queries)
  • userEvent is used in place of fireEvent.
  • asFragment() is used for snapshot testing.

Any background context you want to provide?

N/A

What are the relevant issues?

#5882

Screenshots (if appropriate)

154091194-1c155fed-f663-48e0-9626-e8f4c6d39f04

Do the grommet docs need to be updated?

Yes, after this pr is merged

Should this PR be mentioned in the release notes?

Yes, please

Is this change backwards compatible or is it a breaking change?

backwards compatible

Signed-off-by: GurkiranSingh <gurkiransinghk@gmail.com>
@jcfilben jcfilben added the PRty Biweekly PR reviews by grommet team with hoping of closing such PRs label Jul 6, 2023
@halocline
Copy link
Collaborator

halocline commented Jul 6, 2023

Hi @g4rry420 - Thank you so much for this. This will be very useful. From an API standpoint, I am thinking about the following structure for the connections object type. I think it will allow us the flexibility to extend in the future while aligning with the diagram design tools such as Figma, Adobe, Lucidchart, etc.

{
  type: 'direct' | 'curved' | 'rectilinear',
  endpoint: 'arrow' | { from: 'arrow', to: 'arrow' },  // if string, defaults to both from and to, else use what is specified in object
  ...
}

which in the future could be extended to allow for other endpoint types such as "square", "round", etc.

{
  type: 'direct' | 'curved' | 'rectilinear',
  endpoint: 'arrow' | 'square' | 'round' | { 
    from: 'arrow' | 'square' | 'round', 
    to: 'arrow' | 'square' | 'round' 
  },
  ...
}

…to other endpoint types such as square, round, etc as per Matthew's suggestions

Signed-off-by: GurkiranSingh <gurkiransinghk@gmail.com>
…ypes for endpoint object

Signed-off-by: GurkiranSingh <gurkiransinghk@gmail.com>
@g4rry420
Copy link
Contributor Author

g4rry420 commented Jul 8, 2023

Sounds good, I have made changes and also added a snapshot test, please let me if there are any further changes required :)

markerStart={`url("#openArrowStart-${index}")`}
markerEnd={`url("#openArrowEnd-${index}")`}
/>
{endpoint && arrowMarker && <defs>{arrowMarker}</defs>}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why do we wrap in defs?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The main use case for defs was to holds a set of reusable definitions for the SVG markers. But, it isn't serving it's purpose right now, I will push some change in which we will using arrow based on it's open, close and color.

@@ -222,20 +273,49 @@ const Diagram = forwardRef(({ connections, ...rest }, ref) => {
colorName = colors[index % colors.length];
}

let arrowMarker = null;
Copy link
Collaborator

Choose a reason for hiding this comment

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

This is a smaller comment but to be more flexible for future, should we name this variable endpoint? If needed we can alias the prop as endpointProp.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Since, endpoint is already a prop we are adding in Diagram component, naming the arrowMarker variable to endpointProp will create a confusion as it's expected type to be 'arrow' | { from?: 'arrow'; to?: 'arrow' }. How about if we name this variable as endpointMarker ?
The reason, I have choosed this name - endpointMarker variable is because we are storing the marker tag with the openArrow in it and in future I believe for other endpoints we will be using marker for it. Please, let me know your thoughts

arrowMarker = openArrow(
normalizeColor(colorName, theme),
index,
'openArrowStart',
Copy link
Collaborator

Choose a reason for hiding this comment

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

also to be more flexible for future, should we name this endpointStart since it might not always be an arrow?

@taysea
Copy link
Collaborator

taysea commented Jul 17, 2023

Screen.Recording.2023-07-17.at.1.18.59.PM.mov

@jcfilben @halocline I'm curious your thoughts from a design perspective. Do you think the arrow endpoints should already appear when the line isn't drawn? Or appear only once the line has met the end? Or something else?

@@ -145,16 +159,52 @@ const Diagram = forwardRef(({ connections, ...rest }, ref) => {
toPoint[0] += toRect.width / 2;
if (fromRect.top < toRect.top) {
fromPoint[1] += fromRect.height;

if (typeof endpoint === 'object' && endpoint?.from) {
fromPoint[1] += 10;
Copy link
Collaborator

Choose a reason for hiding this comment

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

How was 10 determined? It might be helpful to add a code comment for future.

Copy link
Contributor Author

@g4rry420 g4rry420 Jul 21, 2023

Choose a reason for hiding this comment

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

I haven't used a definitive approach to calculate the 10. I just check the Animated story and 10 seems good which isn't closely aligned with the start and end of the main diamond diagram

strokeLinejoin={round ? 'round' : 'miter'}
fill="none"
d={d}
markerStart={`url("#openArrowStart-${index}")`}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is there any downside to having the markerStart/markerEnd here if the path doesn't have an arrow?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Also, if multiple diagrams are rendered on a page, will this index id approach work still?

Copy link
Contributor Author

@g4rry420 g4rry420 Jul 21, 2023

Choose a reason for hiding this comment

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

Yes, there is, I will fix that.
Yes, currently, if multiple diagrams are rendered on page, the index approach will not work. I am working on new approach.

@jcfilben
Copy link
Collaborator

jcfilben commented Jul 17, 2023

Screen.Recording.2023-07-17.at.1.18.59.PM.mov
@jcfilben @halocline I'm curious your thoughts from a design perspective. Do you think the arrow endpoints should already appear when the line isn't drawn? Or appear only once the line has met the end? Or something else?

I think my expectation would be that if the arrows are at the endpoints they should only appear once the line has been drawn to the end.

@jcfilben jcfilben removed the PRty Biweekly PR reviews by grommet team with hoping of closing such PRs label Jul 20, 2023
…row marker by utilizing the defs tag

Signed-off-by: GurkiranSingh <gurkiransinghk@gmail.com>
Signed-off-by: GurkiranSingh <gurkiransinghk@gmail.com>
@g4rry420 g4rry420 requested a review from taysea July 22, 2023 02:09
Signed-off-by: GurkiranSingh <gurkiransinghk@gmail.com>
@jcfilben jcfilben added the PRty Biweekly PR reviews by grommet team with hoping of closing such PRs label Aug 3, 2023
@@ -251,6 +415,14 @@ const Diagram = forwardRef(({ connections, ...rest }, ref) => {
connections={paths}
{...rest}
>
{markerElements.length > 0 && (
<defs>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we need defs here?

preserveAspectRatio="xMinYMin meet"
viewBox="0 0 0 0"
>
<defs>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we need defs here?

@taysea
Copy link
Collaborator

taysea commented Aug 17, 2023

Screen.Recording.2023-07-17.at.1.18.59.PM.mov
@jcfilben @halocline I'm curious your thoughts from a design perspective. Do you think the arrow endpoints should already appear when the line isn't drawn? Or appear only once the line has met the end? Or something else?

I think my expectation would be that if the arrows are at the endpoints they should only appear once the line has been drawn to the end.

@g4rry420 I'm still noticing the arrow appearing before the animation is finished. Can you update so the end point arrows only appear once the animation is done?

markerElements.push(
openArrow(
normalizeColor(colorName, theme),
`__grommet__openArrowStart__${normalizeColor(
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is there any value to building this id up based on the id the caller has passed for the from/to of their diagram?

Still wondering if this will cause issues if multiple diagrams are presented on the same screen where we might have clashing id with this current approach.

@jcfilben jcfilben added waiting Awaiting response to latest comments and removed PRty Biweekly PR reviews by grommet team with hoping of closing such PRs labels Aug 23, 2023
Signed-off-by: GurkiranSingh <gurkiransinghk@gmail.com>
g4rry420 and others added 5 commits October 24, 2023 21:45
Signed-off-by: GurkiranSingh <gurkiransinghk@gmail.com>
Signed-off-by: GurkiranSingh <gurkiransinghk@gmail.com>
… if multiple connections of arrows are present in different color for a Diagram

Signed-off-by: GurkiranSingh <gurkiransinghk@gmail.com>
@g4rry420
Copy link
Contributor Author

I'm still noticing the arrow appearing before the animation is finished. Can you update so the end point arrows only appear once the animation is done?

@taysea I am unable to figure out the animation part over here. Can you please help me ?
I have tried using animateMotion tag with mpath but it doesn't seems to work. Please, let me know if I am missing something

@jcfilben jcfilben added PRty Biweekly PR reviews by grommet team with hoping of closing such PRs and removed waiting Awaiting response to latest comments labels Feb 1, 2024
@taysea
Copy link
Collaborator

taysea commented Feb 15, 2024

I'm still noticing the arrow appearing before the animation is finished. Can you update so the end point arrows only appear once the animation is done?

@taysea I am unable to figure out the animation part over here. Can you please help me ? I have tried using animateMotion tag with mpath but it doesn't seems to work. Please, let me know if I am missing something

I haven't tried this locally, but is there a way to conditionally render the arrows based on the animation duration/etc. So, don't have it rendered (or have it visibly hidden) until the animation completes?

@taysea taysea added the waiting Awaiting response to latest comments label Feb 15, 2024
@jcfilben jcfilben removed the PRty Biweekly PR reviews by grommet team with hoping of closing such PRs label Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting Awaiting response to latest comments
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants