Replies: 4 comments 9 replies
-
|
one alternative I proposed:
|
Beta Was this translation helpful? Give feedback.
-
|
proposal by @Fi3:
|
Beta Was this translation helpful? Give feedback.
-
|
@Fi3 also mentioned that SRI might be already violating the since the refactors my detailed knowledge of the application layer is not so fresh anymore, so I'll defer to @GitGab19 + @Shourya742 to confirm whether this is currently true or not |
Beta Was this translation helpful? Give feedback.
-
Btw, I think this statement is quite silly. Nobody can prevent me from writing so smart handling that it always makes a good decision based on the complicated error code. And if I do that, how is this a violation of the specification? Anyways, To be honest, I don't understand this 👇
IMO every submit is at any time either valid or not valid. Everything after SNPH, in example above, is clearly invalid and should be labeled as stale. If rejected, the reason is perhaps not as important. So I don't see any essential use case for automated actions. But on the other hand |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
recently @Fi3 reached out to me pointing out that this section of the spec is too limiting:
We should use this space to coordinate discussions on potential approaches to make this a bit more flexible.
Beta Was this translation helpful? Give feedback.
All reactions