@cline Should we keep the memory-bank files, or should they coexist with the project rules? Currently, the memory bank and the rules contain a lot of overlapping content, which feels redundant.
@cline I have already set up the .clinerules folder, but when I added the memory bank in the custom instructions and created the memory-bank folder structure, i noticed systemPatterns and techContext files contain most of the rules i've written, should i remove the rules files?
@Dimillian It would be great to have a .cursorrules file that helps Composer standardize project structure, ensuring new projects follow the same folder, class, model, and package organization as IceCubes & IcySky
@JordanMorgan10@hijz What's the use-case from returning a value from the intent ? In the GetCaffeineIntent's perform method, i see no benefit from returning an amount, removing the ReturnsValue<Double> and the amount, the code still compiles.
@DonnyWals@setting@StateObject@appstorage I couldn't find a way to use the @Setting wrapper outside of SwiftUI to read/write values into UserDefaults, instead I'm accessing UserDefaults directly which is not the best way I believe.
@DonnyWals@setting The @Setting custom property wrapper you created in the article has the `SettingKeys` property which's defined as a @StateObject, the `SettingKeys` class uses @AppStorage to store app setting values in User Defaults ...
@DonnyWals@setting and at the same time, accessing the UserDefaults.standard in that ObservableObject class as a workaround sounds ugly and not the best way to do it, any thoughts on that are appreciated
@DonnyWals Reading your article about "Writing custom property wrappers for SwiftUI", and wondering how to access the @Setting property wrapper from outside SwiftUI, like accessing it from an ObservableObject class! i know it's not possible and gives the famous runtime error ...
@qwertyui03 هلا اخوي ابو حمزة .. مبارك عليك الشهر وتقب�� الله الطاعات .. انا اخذت مرة عطر IX من فوح، وكان جميل بنكهة الشاي الاخضر والاخشاب .. على حد علمك هل عندهم عطر جميل غيره ؟
@natpanferova while I was migrating my old codebase from ObservableObject to @Observable, in some of my views I listen to property changes using .onReceive and do some logic inside its closure, is withObservationTracking the cleanest equivalent to .onReceive in order to listen to changes ?