Use pathCreator in env page

[goodoldneon]

Description

On that env page, replace all href template literals with pathCreator methods

Type of change (choose one)

• Chore (refactors, upgrades, etc.)
• Bug fix (non-breaking change that fixes an issue)
• Security fix (non-breaking change that fixes a potential vulnerability)
• Docs
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality not to work as expected)

Checklist

• I've linked any associated issues to this PR.
• I've tested my own changes.

Check our Pull Request Guidelines

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 9, 2024 7:03pm

[IGassmann]

@goodoldneon, what do you think of using https://github.com/lukemorales/next-safe-navigation instead?

I played with it a bit, and it worked great! It also handles search params nicely.

We can still use encodeURIComponent on it with Zod.

It's maintained by one of the WorkOS devs.

[goodoldneon]

@goodoldneon, what do you think of using https://github.com/lukemorales/next-safe-navigation instead?

Looks good at a glance! I don't have a preference about what what we use, so long as:

• We aren't hardcoding paths throughout the app
• URL encoding is implicit

[goodoldneon]

After thinking about it a little more, it seems like overkill to add a dependency for the URLs. The existing pathCreator seems fine for this simple use case