feat: basic RfcAuthor API#9940
Merged
jennifer-richards merged 5 commits intoietf-tools:feat/rpc-apifrom Nov 14, 2025
Merged
Conversation
Creates a bunch of API endpoints we have no intention of ever using
rudimatz
approved these changes
Nov 14, 2025
rjsparks
approved these changes
Nov 14, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds basic RfcAuthor management endpoints. Serializer naming is a bit less than ideal because
RfcAuthorSerializeris already in use for the red API. I'll clean that up when I add RfcAuthor support to that API and then rename the serializer.This is similar to purple's
RfcAuthorAPI, but does not provide theset_order()action. We could add that, but I think it's unlikely to be used on this interface. Instead, delete all the existing authors for an RFC and add the correct set from scratch.