Skip to content

Make routes tab great again#204

Merged
AlemTuzlak merged 15 commits intomainfrom
make-routes-great-again
Apr 30, 2025
Merged

Make routes tab great again#204
AlemTuzlak merged 15 commits intomainfrom
make-routes-great-again

Conversation

@AlemTuzlak
Copy link
Copy Markdown
Contributor

Description

Bring back all routes on routes tab instead of discovered ones, show which ones are discovered

Fixes # (issue)

If this is a new feature please add a description of what was added and why below:

Type of change

Please delete options that are not relevant.

  • 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

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Unit tests

Checklist:

  • My code follows the guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings or errors
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new bot commented Apr 29, 2025

Open in StackBlitz

npm i https://pkg.pr.new/forge-42/react-router-devtools@204

commit: 674871e

@AlemTuzlak AlemTuzlak merged commit 5039c35 into main Apr 30, 2025
6 checks passed
@AlemTuzlak AlemTuzlak deleted the make-routes-great-again branch April 30, 2025 14:58
"description": "Devtools for React Router - debug, trace, find hydration errors, catch bugs and inspect server/client data with react-router-devtools",
"author": "Alem Tuzlak",
"version": "1.1.10",
"version": "5.0.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Was this change intentional?

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,it was a mistake to start over from v1 on react-router-devtools as most of the v2-v4 version range was taken by remix-development-tools on this repo so I moved it to 5 to allow for easier releases

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hi, @AlemTuzlak!

Thank you for confirming this information. We're in the process of upgrading to the latest version and noticed this represents a significant version jump. I was interested in understanding the rationale behind this major bump from 1.x to 5.x.

Is this transition documented somewhere? It would be valuable to share this context with customers and users who are planning similar upgrades to ensure a smooth transition.

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.

@fkoner sorry I missed this comment, the reason behind it is that this repo used to be remix-development-tools which has a lot of existing releases in the 2-4 range so I decided to skip to 5 so I don't break releases due to duplicate versions. I should've started from the beginning with v5

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