readability edits for CEP-21#130
Conversation
| > * (Typed) repodata parsers would need to be updated to handle the new field. | ||
|
|
||
| We propose that these reasons no longer hold with [sharded repodata](https://github.com/conda/ceps/blob/main/cep-0016.md). |
There was a problem hiding this comment.
Lack of newline here causes a very confusing render
| **It would require extending the repodata schema, currently not formally standardized.** | ||
| ### Re: "It would require extending the repodata schema, currently not formally standardized." |
There was a problem hiding this comment.
The screenshot above also shows that the current highlight makes it seem like part of the regular text of the CEP. I don't care about the exact formatting, as long as it is clear that it's a point being addressed.
|
I understand the edits but now the part about that the run exports are stored inside the repodata is part of the discussion. Maybe we should then clarify this in the (new) specification section with MUST? |
|
I don't know the process for editing accepted CEPs; in any case, I rely on you the author to make those changes, I just wanted to get the ball rolling. :) If you want I can give you collaborator rights on my fork, then you can push directly into this PR. |
2 participants
While reading https://github.com/conda/ceps/blob/main/cep-0021.md for work on #129, I noticed some minor issues, which I'm suggesting to fix here.
The big issue that I don't know how to fix is that the "Specification" section is IMO mislabeled, as it only contains discussion of reasons that CEP 12 had brought for not embedding run-exports into the regular repodata. The only language that uses authoritative keywords (MAY, MUST) is under "Patching" (though that's also mixed with non-technical language, e.g. "We do not see a reason how [...]"), so presumably that must be the entirety of the specification?
CC @baszalmstra