You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a really interesting idea! In general, for this kind of thing, I've tended to do two things:
Prototype it in my own operator's base component class (you could probably do this now)
Add it to oper8.x.oper8x_component
In general, I've tried to avoid adding too many optional bells-and-whistles to the base Component, but since this would just wrap self.add_resource, it would be a natural fit for the "Component plus common patterns" base in oper8.x. I don't think you guys are using oper8.x though, are you? It also gets you other nice things like the deps_annotation to auto-rollover on mounted data changes.
Understood, that makes sense to me. I was in the middle of 1 prior to opening the issue, completely missed oper8.x. I'll dig more into that now as the deps_annotation was on my todo list as well. Thank you!
Is your feature request related to a problem? Please describe.
Not a major problem, right now I'm implementing a feature to ignore certain nodes that are annotated in a certain way. This looks roughly like
Describe the solution you'd like
I'd love to be more clear on whether a resource has some condition that needs to be satisfied first. In my head this looks like
which turns the above example into
Describe alternatives you've considered
Could also enhance existing
add_resource
with an additional param, I suggested a separate method to be more clearAdditional context
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: