[FRONT] fix(db): correct contacts table name typo#491
Merged
jb-delafosse merged 1 commit intomainfrom Feb 15, 2026
Merged
Conversation
Contributor
|
Preview is deploying...| ℹ️ Name | 🔗 Infos & links |
|---|---|
| 🌱 Deploying commit | df1e481 |
| 👁️ Preview | Generating preview app... |
Fix typo in DataTable enum: 'communties_contacts' -> 'communities_contacts' This typo was introduced in commit d117231 and caused queries to the contacts table to fail with 'relation does not exist' error, resulting in HTTP 500 on /interpeller/[siren]/step2 route. no_jira
jb-delafosse
force-pushed
the
fix/contacts-table-name-typo
branch
from
df1e481 to
4c1fe81
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.
Summary
Fix typo in
DataTableenum:communties_contacts→communities_contactsThis typo was introduced in commit d117231 (May 2025) when the Contacts enum was first added. The frontend has been querying a non-existent table, causing HTTP 500 errors on
/interpeller/[siren]/step2.Root Cause
communities_contactscommunties_contacts(missing "i")Test Plan
/interpeller/[siren]/step2no longer returns HTTP 500