| 26 Jul 2025 |
emily | hasn't been since 25.05 | 09:54:28 |
emily | that's why the nitpicking is dumb | 09:54:32 |
emily | we will remove the warning after a release cycle | 09:54:41 |
niklaskorz | the warning or the attribute? | 09:54:54 |
emily | and it will become an implicit derivation var like all other mkDerivation args | 09:54:55 |
emily | the warning. the attribute doesn't exist (after the -next PR) | 09:55:08 |
emily | it's just an ignored argument | 09:55:18 |
niklaskorz | I see, perfect | 09:55:25 |
emily | In reply to @tomasajt:matrix.org I will be away for a week, so I wont be able to handle this myself
But I'd say the warning PR should be like `useFetchCargoVendor ? null` and `warnIf (useFetchCargoVendor != null) ......`
About whether we merge the main PR now: uuhhh, I'm leaning towards not wating for stable, but IDK
maybe args ? useFetchCargoVendor is better | 09:55:42 |
Toma | That is better | 09:56:35 |
emily | thanks for all the work you've done lately btw. try not to check notifications too much while you're away :) | 09:56:59 |
emily | In reply to @emilazy:matrix.org maybe args ? useFetchCargoVendor is better we will also need to reword the throw for the false case to just tell people to remove it | 09:57:24 |
niklaskorz | "+1“ on that! | 09:57:24 |
emily | and then after branch-off we drop 'em both | 09:57:35 |
emily | or rather | 09:57:40 |