@goynang@JasonHassold@jessfraz In my experience the consistency in your styling with Tailwind is provided by an underlying design system, so each component can have "random" styling but within a defined range.
@rfleury This is a constant annoyance in VSCode—just let me spam the close file keyboard shortcut to close all my open files without closing the editor as well!
Hello, iPad! Don't be scared, this isn't a stretched-out iPhone app 👻
To celebrate, we're giving away an 11-inch iPad Pro (M4)!
Copilot Money for iPad is an extension of our powerful Mac app. It takes full advantage of the available screen size and the different ways you can interact with this device. Tracking your finances in one place has never been easier.
🎁 To enter the giveaway, simply repost this announcement and we'll pick a winner on Monday Nov 4th.
I guess there's no real need for Webpack to *resolve* this import at compile time because it can just reference that function while bundling, but it does seem like something it should be able to catch.
Any Webpack wizards on my timeline? I was under the impression that it would throw an error if it encountered something like this:
import { notExported } from './MyFile.js';
Where notExported is a function in MyFile, but is missing the `export` keyword. But it doesn't?
Please don't name your variables `renderTable` or `showIcon`. It is not helpful to read:
{ renderTable ? <Table data={data} /> : null }
If we should render it, we render it. Thank you, Captain Obvious 🦸
Instead, try to name variables for what they represent:
@jmduke Ah, that's cool, I could see myself using that. I think the canonical example always seems a bit remote to me because I'm usually using some form of JS state already to manage form logic, so I'm used to handling things there—but I guess that's exactly what you're talking about!
@Caltrain isn’t it supposed to be a rule that trains never depart early? Was just very sad to watch from the platform as the NB 4:36 from Hillsdale departed at 4:35 😢