Hello everyone,

Hello everyone,

I wanted to address something that has been on my mind regarding
***@***.***` and ***@***.***`. I understand there might be some
confusion or a feeling that they should be avoided in certain situations,
perhaps due to previous experiences with unexpected bugs or rendering
issues, especially when integrated with `NotificationCenter`.

However, it's crucial to remember that ***@***.***` and ***@***.***`
play a vital role in SwiftUI's state management, particularly for
view-specific data. They are designed to manage the lifecycle of observable
objects within the context of a view, ensuring that the view correctly
reacts to changes in its associated view model.

Rather than considering their deletion or avoidance, I believe the key lies
in understanding their appropriate use cases and how they interact with
other architectural patterns, such as `NotificationCenter`. As TAENI kindly
explained earlier in the thread, the issues arise when ***@***.***` or
***@***.***` are misused in scenarios where a broadcast state is
needed, leading to untraceable bugs. This isn't a fault of the property
wrappers themselves, but rather a misapplication of their intended purpose.

Let's not remove these powerful tools from our arsenal. Instead, let's
focus on deepening our understanding of when and how to leverage them
effectively to build robust and maintainable SwiftUI applications.

Thanks,
Vincent

On Thu, Jul 10, 2025 at 19:03 SSOL ***@***.***> wrote:

> ***@***.**** approved this pull request.
>
> User Notification과의 차이점, 사용해야 하는 상황과 아닌 상황이 구분되어있어서 좋았어요! 로그인 이벤트 코드 예시가
> 있으니까 직관적으로 잘 이해됩니닷 수고 많으셨어요~!
>
> —
> Reply to this email directly, view it on GitHub
> ,
> or unsubscribe
>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***
> com>
>

_Originally posted by @observableobject in https://github.com/DeveloperAcademy-POSTECH/2025-SSG-M5/pull/82#issuecomment-3056573803_