Skip to content

Fix conflicting requirements for post/info key 'accept-role'#30

Open
cblgh wants to merge 1 commit into
mainfrom
fix-accept-role-requirement
Open

Fix conflicting requirements for post/info key 'accept-role'#30
cblgh wants to merge 1 commit into
mainfrom
fix-accept-role-requirement

Conversation

@cblgh

@cblgh cblgh commented Mar 1, 2025

Copy link
Copy Markdown
Member

On merging the request for comments PR with the addition of a new key for post/info—a result of the moderation protocol being created—the new key, accept-role, had a change in its requirements from SHOULD to be RECOMMENDED. But during the merge something went wrong, causing accept-role to be listed as both RECOMMENDED and MUST, while the spirit of the change was to make it a recommendation.

This commit remedies the conflicting requirements.

On merging the [request for comments
PR](#23) with the addition of a new key
for `post/info`--a result of the moderation protocol being created--the new
key, `accept-role`, had a change in its requirements from SHOULD to be
RECOMMENDED. But during the merge something went wrong, causing `accept-role` to be listed
as both RECOMMENDED and MUST, while the spirit of the change was to make a
recommendation.

This commit remedies the conflicting requirements.
@hackergrrl

Copy link
Copy Markdown
Member

Makes sense to me. 👍🏻

Do you think it's worth bumping the draft version number? My own preference would be to, just to prevent any ambiguity.

@cblgh

cblgh commented Apr 5, 2025

Copy link
Copy Markdown
Member Author

Do you think it's worth bumping the draft version number? My own preference would be to, just to prevent any ambiguity.

I don't mind either way! My pov: for typos that do not affect behaviour I don't think it's needed but this is kind of straddling the line, so I think your preference to do so is probably wise :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants