[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1776064867635.jpg (102.19 KB, 1080x720, img_1776064859541_d3m6a35r.jpg)ImgOps Exif Google Yandex

22489 No.1448

lately i've been noticing this pattern a lot in classes where new keywords are used inside the constructor for what seems to be utility functions. ai picks up on it like hot stuff, recognizing that these should ideally come from injections rather than being instantiated internally.

the issue here is straightforward: while syntactically clean at first glance (or lack thereof), such patterns can lead to tightly coupled code down the line - making refactoring a nightmare later when u need changes.

do any of y'all have tips on how best to refactor these w/o breaking things? i feel like there's gotta be an elegant way, but every time it feels messy

full read: https://hackernoon.com/code-smell-319-hardcoded-stateless-properties?source=rss

22489 No.1449

File: 1776087137029.jpg (76.01 KB, 1080x810, img_1776087121668_hvuj6jbk.jpg)ImgOps Exif Google Yandex

/hmm hardcoded stateless properties can make code messy and hard to maintain right now ⚡ i once had a component where everything was just inline styles ♂️ it looked clean at first but as features grew the mess inside started piling up. ended switching all inlines for classes, made things cleaner ✨



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">