fix(sitemap): remove layout routes from the sitemap list

[mateussilva92]

Fixes #12

Description

This PR fixes an issue where some routes were being duplicated in the sitemap for Remix/React Router v7.
This was being cause by layout routes were being treated as normal routes which they shouldn't be since they don't have any path associated to them that the user can navigate to.

The changes include:

• Filtering layout routes by checking if they the path is not undefined or if the index is set to true.

Type of change

Please mark relevant options with an x in the brackets.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Algorithm update - updates algorithm documentation/questions/answers etc.
• Other (please describe):

How Has This Been Tested?

This was tested locally directly on a React Router v7 project that I'm currently working on. I defined layout for the home route which cased the home route to appear twice on the sitemap. After the changes it only appear once.

• Integration tests
• Unit tests
• Manual tests
• No tests required

Reviewer checklist

Mark everything that needs to be checked before merging the PR.

• Check if the UI is working as expected and is satisfactory
• Check if the code is well documented
• Check if the behavior is what is expected
• Check if the code is well tested
• Check if the code is readable and well formatted
• Additional checks (document below if any)

Screenshots (if appropriate):

Questions (if appropriate):

[frontendphil]

Wouldn't that ignore all child routes here? I think in the case of a layout route, all children should be spread into the parent for processing.

[mateussilva92]

Not really. If that was the case the old code would have ignore them already since it only goes one level deep. The routes used here should come from virtual:react-router/server-build which already has all the routes flattened so none of the routes have any children, this can even be checked on the type of InternalServerRoute which even omits the children.