Validation rule for unicity of path+label #37
-
This is kind of a follow-up to #35. Would it make sense to have a rule to enforce unicity of path+label? The spec currently says:
In certain cases, for instance, query GetHero {
hero {
...heroDetails1 @defer
...heroDetails2 @defer
}
} it is guaranteed that path+label won't be unique and it could be detected. I guess the question can be summarized as:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
This was written when label was still a mandatory argument. I think it should be updated now that we've agreed that it should be optional. It was meant to inform that neither the path nor label could be used to uniquely identify payloads, both are required. I think I will change it to something like
|
Beta Was this translation helpful? Give feedback.
This was written when label was still a mandatory argument. I think it should be updated now that we've agreed that it should be optional. It was meant to inform that neither the path nor label could be used to uniquely identify payloads, both are required. I think I will change it to something like