Skip to content

Keep ranges open #1041#1092

Merged
demiankatz merged 3 commits intoUniversalViewer:devfrom
Saira-A:1041
Aug 30, 2024
Merged

Keep ranges open #1041#1092
demiankatz merged 3 commits intoUniversalViewer:devfrom
Saira-A:1041

Conversation

@Saira-A
Copy link
Copy Markdown
Contributor

@Saira-A Saira-A commented Aug 22, 2024

Description of what you did:

Keeps range open when node selected in index view #1041

@vercel
Copy link
Copy Markdown

vercel bot commented Aug 22, 2024

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Comments Updated (UTC)
universalviewer βœ… Ready (Inspect) Visit Preview πŸ’¬ Add feedback Aug 27, 2024 4:06pm

@LanieOkorodudu
Copy link
Copy Markdown
Collaborator

Thanks @Saira-A I just tested in Vercel app and it works fine. πŸ‘ .Well done!

Copy link
Copy Markdown
Contributor

@demiankatz demiankatz left a comment

Choose a reason for hiding this comment

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

Thanks, @Saira-A -- just a couple quick questions/comments.

const currentCanvasTopRangeIndex: number = this.getCurrentCanvasTopRangeIndex();
const selectedTopRangeIndex: number = this.getSelectedTopRangeIndex();
const usingCorrectTree: boolean =
const currentCanvasTopRangeIndex = this.getCurrentCanvasTopRangeIndex();
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The only changes to this particular function seem to be removing types. Just curious if there's a reason for that. If the types were unnecessary because of inference, then I have no objections... I'm not familiar with all the subtleties of when it's best to type or not type -- but the change just stood out so I thought I'd ask. :-)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes, I removed the types because I didn't think the explicit type annotation was necessary but I'm not an expert so I can back to how it was to be just in case :)

Copy link
Copy Markdown
Contributor

@demiankatz demiankatz left a comment

Choose a reason for hiding this comment

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

Thanks, @Saira-A, this looks good to me -- one last comment in case you want to tighten things up a little more, but it doesn't need to stand in the way of approving the PR. :-)


public getAllNodes(): TreeNode[] {
return this.treeComponent.getAllNodes();
const allNodes = this.treeComponent.getAllNodes();
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Did you refactor this (and the method below) for debugging purposes? If so, should they be put back the way they were now that you're done? (If there's a reason to change a one-liner into a two-liner, I don't really mind -- but otherwise it might be better to remain concise).

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.

Tested again today in the Vercel app, and it looks good. The fix has addressed and resolved the issue #1041. Thanks again @Saira-A πŸ‘

@demiankatz
Copy link
Copy Markdown
Contributor

Thanks, @Saira-A and @LanieOkorodudu! Merging now.

@demiankatz demiankatz merged commit ee2738c into UniversalViewer:dev Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Completed

Development

Successfully merging this pull request may close these issues.

3 participants