- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Jan 2023 18:04:49 +0000
- To: public-hydra-logs@w3.org
Yes, I fully agree. It can be very useful to let clients know why an operation is disabled. Not only hide it in the UI The composite approach is possible but cumbersome where you need many classes added dynamically. ________________________________ From: Jánszky Lajos ***@***.***> Sent: Friday, 6 January 2023 18:59 To: HydraCG/Specifications Cc: Tomasz Pluskiewicz; Mention Subject: Re: [HydraCG/Specifications] Retracting operations (PR #246) I thought about this more. The main reason I think the composite approach is not the best, because we don't know the reason why a certain operation is not available. If we return it to the client explicitly and they expect it, then they can solve the issue easier. Though this appears to be some sort of debug related problem for a debug mode, not something one would generally expect. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***> -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/246#issuecomment-1373966859 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 6 January 2023 18:04:50 UTC