feat: add routing icon support for *.route.ts and *.route.tsx

[Vaibhav-Naik-26]

Description

• Added support for *.route.js, *.route.jsx, *.route.ts and *.route.tsx files to show the routing.svg icon, similar to existing *.routes.js, *.routes.jsx, *.routes.ts and *.routes.tsx.

• This change ensures that single route files (common in routes/ folders) get the correct icon, improving consistency.

Contribution Guidelines

• By creating this pull request, I acknowledge that I have read the Contribution Guidelines for this project
• I have read the Code Of Conduct and promise to abide by these rules

[PKief]

From my point of view the current icon isn't such a good fit for single route files. The icon currently shows a way sign which typically shows multiple routes. If we associate the icon to a single route it doesn't feel like a good fit from my point of view. This icon is rather made for route configs where multiple routes are configured than for a single route file.

[Vaibhav-Naik-26]

I completely understand the point you're raising. Just to clarify the structure we're using:

In my project, I have a routes/ folder where each file is responsible for defining a set of related routes for a specific resource (for example, user.route.ts defines all the routes for the user resource — listing users, creating users, deleting users, etc.).

Here's an example of what a typical file (user.route.ts) looks like:

import { createUser, deleteUser, getAllUsers, getUserById } from '../controllers/user.controller.js';
import { Router } from 'express';

export const router = Router();

router
  .get('/', getAllUsers)
  .get('/:id', getUserById)
  .post('/create', createUser)
  .delete('/:id', deleteUser);

Even though each file focuses on one resource, it still defines multiple routes (GET, POST, DELETE, etc.), which is why I felt the current routing.svg icon was appropriate. These files are part of the overall routing layer, just structured in a more modular way.

My intention was to make all route-related files visually consistent, regardless of whether they handle the full app’s routes (routes.ts) or just a specific resource’s routes (user.route.ts). This naming and structure is fairly common in Express projects.

[PKief]

Okay, let's give it a try. Your argumentation makes sense to me as well.

[github-actions]

Merge Successful

Thanks for your contribution! 🎉

The changes will be part of the upcoming update on the Marketplace.