Last week we released a new version of DCM 🔥! - 9 new rules and 9 quick fixes - new command for analyzing image assets - reworked docs for rules - duplicate tests detection - and more: https://lnkd.in/dieshSBy Let's go through the release highlights: 1. New command for analyzing image assets. Helps you address various image-related issues: exceeding size, incorrect naming, incorrect placement, incorrect formats and issues with missing or unused high-resolution images. https://lnkd.in/dJG2pYqX 2. Duplicate test cases detection. "check-code-duplication" now supports detecting duplicate test cases! To get such reports, simply run this command agains your test folder: "dcm check-code-duplication test". https://lnkd.in/dkk__a6U 3. Reworked documentation for rules. We've updated all rule docs to have a better highlight region and a proper warning message to help you understand what problem the rule tries to address. The description for some rules has also been updated for that same reason. Additionally, most rules with additional configuration now have new examples specifically for their config options. For example: https://lnkd.in/dvafqRFg 4. There is more! To learn about other updates and new features, check out the release article: https://lnkd.in/dieshSBy
DCM Analyzer’s Post
More Relevant Posts
-
Ready to Level Up Beyond console.log()? 💻 We’ve all leaned on console.log() for debugging—it’s quick, simple, and kind of a habit. But have you noticed how it can clutter the console and sometimes even slow things down? If you’re tired of the chaos, there are actually some awesome console methods out there that can make debugging way more efficient (and your console a lot cleaner). Here’s What to Try Instead: 1. console.dir() – Need to see deep into an object’s structure? console.dir() gives you a clearer view. 2. console.clear() – Sick of scrolling? console.clear() wipes out old logs so you’re only seeing what matters right now. 3. console.group() – Want organized logs? Use console.group() to create collapsible sections, keeping related info grouped together. 4. console.table() – Got data? View arrays and objects in a nice table format. It’s way easier on the eyes. 5. console.time() – Tracking performance? console.time() and console.timeEnd() help you see exactly how long things are taking. A Few Tips: • Keep Production Logs Clean – Clear out logs before going live. They can expose data and slow things down. • Use Log Levels – Set up logs by level (info, warn, error), making it easy to filter for what you need. Next time, instead of reaching for console.log(), give these a shot! Here’s a great read that dives deeper: https://lnkd.in/db4FwADj Happy debugging! 🛠️ #WebDev #JavaScriptTips #CodingLife #DevHacks #ConsoleTips
To view or add a comment, sign in
-
👨💻 In a recent article, Abdelrahman Seada discusses efficient methods for conditional rendering in React applications. ✨ He suggests replacing traditional 'if...else' statements and ternary operators with a more streamlined approach using objects to map user types to their corresponding actions. 🛠️ By structuring user actions in an object, developers can simplify the rendering logic, making the codebase cleaner and more maintainable. ✅This method not only reduces complexity but also enhances readability and scalability. 🔗 For a detailed explanation and code examples, you can read the full article here: https://lnkd.in/e2rUCRCB
To view or add a comment, sign in
-
If you recently joined a company as a frontend developer, then this is for you. Irrespective of the task level you got assigned, attach an image or Jam.dev of your work to the PR. Why? Even though it might sound like a trivial change to you, it might not be for the person reviewing. If visual feedback is missing in the PR, then the person has to checkout the branch and review it. This adds a lot of friction and slows down the review process. Of course, some good companies can raise live preview for each PR which makes this process easier but still they have to navigate to the respective page or component. Just attach an image or Jam.dev to your PRs and reduce the friction. Trust me, everyone on the team will appreciate this effort. Once you better understand the product, you might be okay with not doing such PRs and sticking to more text-based ones. Here is a nice example of such PR raised by Anmol Bhatia from the Plane team: https://lnkd.in/g_ngsf5R #betterreviews #pr #github
To view or add a comment, sign in
-
With my newfound RSI, it's finally time to use my new keyboard: a dactyl 3x6 split with Engram layout. But firstly, how should I practice? I discovered an online keyboard practice app at https://keybr.com for the first time this morning. The project is open source, so I was able to: - Download the repository - Add the feature: repeat multiple words between 1-10 times, instead of 1-2 times. - Raise a PR It's already been merged and the owner fixed some cosmetic preferences, and it's now LIVE! What a time to be alive. https://lnkd.in/g8g78HC9 #RSI #MechanicalKeyboard #EngramLayout #OpenSource #Developer #KeyboardPractice #GitHub #Coding #SoftwareDevelopment #Tech #React #UI #Frontend
To view or add a comment, sign in
-
📸 AndroidUiTestingUtils 2.3.5 is out! https://buff.ly/3t2EC19 ✅ Bugfix for FontSizeTestRule, also affecting ActivityTests This 🐞 has been in since 2.3.0 🔜 What's coming next 1. Cross-Library updates to catch up with - Android-Testify 3.1.0 - Roborazzi 2.24.0 - Paparazzi 1.3.4 2. 🎨 DynamicColorTestRule If you're missing any TestRule, feel free to open an issue 😉
To view or add a comment, sign in
-
Excited to Share My Latest Project: A Mini Social Media App! Key Features: -MVC Architecture: Organized the application structure using the Model-View-Controller pattern for clean and maintainable code. -Session-Based Authentication: Implemented user registration, login, and logout functionalities with bcrypt for password hashing and middleware to protect routes. -Database Relationships: Leveraged Sequelize ORM to set up models with one-to-many (User-Post, Post-Comment) and one-to-one (User-Profile) relationships. -EJS Templates: Created dynamic views for user registration, login, profiles, posts, and comments. -CRUD Operations: Enabled authenticated users to create, update, and delete their own posts and comments. -Validation & Error Handling: Ensured data integrity and provided meaningful error messages to users. -Bonus Features: Added pagination for posts and comments, along with a reset password feature. Project Repo : https://lnkd.in/dsn4FPdf
To view or add a comment, sign in
-
PCF Controls are some of the unsung heroes in the Power Platform story, capable of fantastic reuse but still hamstrung by a slightly old school set of tooling. Here's a take on the dev effort for building a control that uses the Dataverse Fuzzy Search API to replace a standard Lookup control. You can find it on PCF Gallery https://lnkd.in/eiHYrrca #PowerPlatform #PCF #Dataverse #fuzzylogic #PowerApps
To view or add a comment, sign in
-
https://lnkd.in/ezSMwvH9 is awesome is would be better if there is an integration with the current useActionState in nextjs
To view or add a comment, sign in