Skip to content

ensure that past visits and reports subroutes also display the selected nav#53

Closed
jgravois wants to merge 1 commit intoasalant:masterfrom
jgravois:more-selected-nav-links
Closed

ensure that past visits and reports subroutes also display the selected nav#53
jgravois wants to merge 1 commit intoasalant:masterfrom
jgravois:more-selected-nav-links

Conversation

@jgravois
Copy link
Copy Markdown
Contributor

just a small tweak to help the routes below display a selected nav option in the header.

  • /[org]/visits/2020/1/17
  • /[org]/visits/2020/1/16 (etc.)
  • /[org]/reports/people
  • [/org]/reports/visits (etc.)

Screen Shot 2020-01-18 at 11 56 13 AM

Copy link
Copy Markdown
Owner

@asalant asalant left a comment

Choose a reason for hiding this comment

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

Thanks! See my review comment.

elsif label === 'Visits'
"<li class='#{request.path.include?('/visits/') ? 'selected' : ''}'><a href='#{path}'>#{label}</a></li>"
else
"<li class='#{request.path.start_with?(path) ? 'selected' : ''}'><a href='#{path}'>#{label}</a></li>"
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

It seems like this line or something similar should be all that is needed to replace the original request.path == path check. Do we need the three checks?

Copy link
Copy Markdown
Contributor Author

@jgravois jgravois Jan 21, 2020

Choose a reason for hiding this comment

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

if we only use start_with, 'Home' will also be selected when folks visit the Visits/Reports/Settings routes.

if I knew as much about ruby as I do about JS I could have condensed the other two by separating the root of the default 'Visits' path from today's date, but I took the easy way out.

Copy link
Copy Markdown
Contributor Author

@jgravois jgravois Jan 21, 2020

Choose a reason for hiding this comment

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

this would probably work.

if label === 'Home' || label === 'Settings'
    "<li class='#{request.path == path ? 'selected' : ''}'><a href='#{path}'>#{label}</a></li>"
else
    "<li class='#{request.path.include?('/' + label.downcase + '/') ? 'selected' : ''}'><a href='#{path}'>#{label}</a></li>"

I'll find some time to make sure soon.

Copy link
Copy Markdown
Contributor Author

@jgravois jgravois Jan 21, 2020

Choose a reason for hiding this comment

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

nope, AFAICT, the two pesky routes below make it pretty tough to cram all the logic you'd need in without a third clause.

  • /[org]/reports
  • /[/org]/reports/visits

if /[org]/reports/ was served up with a trailing slash, it'd be a different story.


edit: I'm a bit hindered here by the fact that I don't even know how to set breakpoints or inspect variables in Ruby/Rails.

if I knew how to do that, I'd imagine I could split the path up using a regex to isolate the portion of the route that comes immediately after the organization name and compare that to the label instead.

@jgravois
Copy link
Copy Markdown
Contributor Author

superceded by #54

@jgravois jgravois closed this Jan 22, 2020
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