Conversation
liamwhite
force-pushed
the
affordances-characterization
branch
from
September 6, 2026 18:07
5fee186 to
eb61609
Compare
liamwhite
force-pushed
the
affordances-characterization
branch
from
September 16, 2026 00:30
eb61609 to
51bcac9
Compare
liamwhite
force-pushed
the
affordances-characterization
branch
from
September 16, 2026 00:45
51bcac9 to
b4581ff
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Like #708 but for current rendering policy. Pinning these so that they can serve as regression tests for a planned refactor which will move all remaining rendering policy into the application (so that it's not literally all duplicated into the controllers/views when we make the next API revision)