Repository navigation
fix(dev): маршруты API приглашений и шаблонов решений - #835
Merged
Merged
Conversation
This was referenced Oct 26, 2026
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
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.
Что изменено
DEV Nginx проксирует существующие C00 namespaces
/solution-invitations/и/solution-form-templates/в Django. До исправления они попадали в Angular SPA:HTTP200 HTML, ошибка JSON parsing в уведомлениях. Путь решения внутри/programs/уже работал.API / UI
Контракты, Angular и бизнес-правила не менялись. Новые API paths получают ответы Django (включая401 JSON без авторизации), существующий allowlist auth SPA и остальные namespaces сохранены.
Permissions
Backend authentication/object permissions сохранены; новые regex alternatives имеют прежнюю границу
/|$. Похожий SPA URL/solution-invitations-aboutостается SPA. Изменяется только DEV config, production не затрагивается.Проверки
Риски / migration
Миграций нет. В post-deploy routing smoke добавлены обе проверки401 JSON, чтобы повторная потеря proxy namespace останавливала выкладку. Изменений старых программ, проектов или данных нет.