app: fix custom session routes with path prefix #1093
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Summary
When running litd using a path-prefix (ex:
PUBLIC_URL=/lit), the route navigation is not working properly. It navigates to/connectinstead of/lit/connect. The fix was simply to ensure the new route is always prefixed with thePUBLIC_URLenv var.Screenshots
This is what currently happens when using a path prefix on
masterlitd-path-prefix-custom-session-broken.mp4
This shows the functioning flow when using this PR
litd-path-prefix-custom-session.mp4
Steps to Test
/litprefix)Related Issues & Pull Requests
Closes #1058