Skip to content

Add competency fixture for renamed setting mappings #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
bpstr wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Add competency fixture for renamed setting mappings #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions tests/fixtures/competency/renamed-setting-mapping/SCENARIO.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# Renamed setting across API and frontend

Question: Do the API and frontend enforce the same attachment-size setting despite different identifiers?

Expected: trace the concrete values/usages and represent the mapping as evidence-backed or inferred; lexical name equality is neither required nor sufficient.
4 changes: 4 additions & 0 deletions tests/fixtures/competency/renamed-setting-mapping/api/config.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
MAX_ATTACHMENT_BYTES = 10485760

def attachment_limit():
return MAX_ATTACHMENT_BYTES
2 changes: 2 additions & 0 deletions tests/fixtures/competency/renamed-setting-mapping/web/upload.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
export const maxUploadSize = 10 * 1024 * 1024;
export function acceptsUpload(bytes: number) { return bytes <= maxUploadSize; }
Loading