ColdFusion Coding Standards
ColdFusion cfm files and application patterns
स्किल
# ColdFusion Coding Standards - Use CFScript where possible for cleaner syntax. - Avoid using deprecated tags and functions. - Follow consistent naming conventions for variables and components. - Use `cfqueryparam` to prevent SQL injection. - Escape CSS hash symbols inside <cfoutput> blocks using ## - When using HTMX inside <cfoutput> blocks, escape hash symbols (#) by using double hashes (##) to prevent unintended variable interpolation. - If you are in a HTMX target file then make sure the top line is: <cfsetting showDebugOutput = "false"> # Additional Best Practices - Use `Application.cfc` for application settings and request handling. - Organize code into reusable CFCs (components) for maintainability. - Validate and sanitize all user input. - Use `cftry`/`cfcatch` for error handling and logging. - Avoid hardcoding credentials or sensitive data in source files. - Use consistent indentation (2 spaces, as per global standards). - Comment complex logic and document functions with purpose and parameters. - Prefer `cfinclude` for shared templates, but avoid circular includes. - Use ternary operators where possible - Ensure consistent tab alignment.
इसे कैसे लगाएं
1. Open the tool and start a new conversation, project or template. 2. Paste the text below wherever the tool keeps standing instructions — usually called system prompt, instructions, or persona. 3. Save it so it applies to every run rather than a single message.
क्या यह आपके काम आई?
यहाँ लिखने के लिए साइन इन करें।यह कहाँ से आई
GitHub, Inc.