.env.example or .example.env so IDEs and code editors can do syntax highlighting and linting

Created on 15 January 2025, 7 days ago

Problem/Motivation

This is an inquiry, not a request to change things in this module.

I noticed files like env.example dont get syntax highlighting. I thought about changing to example.env so IDEs and code editors know what type of file it is.

Do you have a workaround or other solution or idea you all use that maybe I can use too?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request

Status

Active

Version

1.2

Component

Documentation

Created by

🇺🇸United States yesct

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @yesct
Comment 7 days ago →
🇧🇪Belgium dieterholvoet Brussels
I think .env.* is the way to go, it's the way Symfony, Vite, Next.js and others do it. If your editor doesn't recognize these files, maybe there's a plugin you can install or a binding you can set up yourself.
Comment 4 days ago →
🇧🇪Belgium dieterholvoet Brussels

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024