Field names at exactly the length limit are wrongly rejected

An owner trying to create a form with a field name that happens to be exactly 100 characters long gets a confusing rejection -- "'name' exceeds 100 characters" -- even though the name does not exceed 100 characters, it equals it. This is a paper-cut for a human typing a long field name by hand, but it is a sharper edge for anyone integrating programmatically: a script that trims field names to the documented 100-character limit before submitting will get inconsistent 422s depending on whether the trimmed name happens to land at exactly 100 characters, with no obvious explanation in the error message for why an apparently within-limit name was rejected. Low severity, but exactly the kind of thing that generates a confused support ticket ("your docs say 100, I sent 100, it failed") that costs real time to triage.

validate_field_definitions() is supposed to reject field names longer than MAX_FIELD_NAME_LEN (100 characters). Right now it also rejects names exactly at that length.

cd flask/feedback_service export FLASK_ENV=testing .venv/bin/python -c " from app import create_app from app.extensions import db

app = create_app('testing') with app.app_context(): db.create_all() client = app.test_client()

reg = client.post('/api/auth/register', json={'email': 'a@example.com', 'password': 'supersecret123'}) token = reg.get_json()['access_token'] headers = {'Authorization': f'Bearer {token}'}

name_100 = 'x' * 100 resp = client.post('/api/forms', json={'title': 't', 'fields': [{'name': name_100, 'type': 'text'}]}, headers=headers) print(resp.status_code, resp.get_json()) "

Expected: 201. Actual: 422 with "fields[0]: 'name' exceeds 100 characters"

MAX_FIELD_NAME_LEN = 100 is documented (by the error message itself, and by convention) as the maximum allowed length, not the first disallowed length. A value of exactly the limit satisfying "exceeds the limit" is a classic boundary/off-by-one mistake, and it is worth practicing spotting these because they are extremely common in real input-validation code (pagination limits, string-length checks, rate windows, buffer sizes -- the same shape of bug shows up everywhere).

Look at the single comparison in validate_field_definitions that decides whether a field name is too long. Compare it, character by character, against what the error message it produces actually claims ("exceeds N characters"). Python's comparison operators are exact tools here -- make sure the one used matches the English in the error string.