Prod: expose vacancy catalog applicant actions - #720
Merged
TThanos3000 merged 1 commit intoAug 30, 2026
Conversation
TThanos3000
marked this pull request as ready for review
August 30, 2026 21:26
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.
Что изменено
Semantic port проверенной функциональности DEV PR #719 поверх production vacancy architecture:
VacancyApplicantStateSerializerMixin;VacancyCatalogSerializerвозвращает read-onlyhas_responded,response_status,can_respond,can_manage_responses;VacancyListприменяет существующий production selectorwith_applicant_state()кget_public_vacancies_queryset();Production
vacancy/managers.pyне переносился: каталог уже построен наget_public_vacancies_queryset(),_vacancy_queryset()и production public-profile selectors. Сохранены текущая публичная фильтрация, prefetch/select_related, pending response count, detail contract и response lifecycle.Проверки
CI:
No changes detected;Локально:
manage.py check --tag models— пройден;makemigrations --check --dry-run --skip-checks—No changes detected;git diff --check— пройден;Локальные DB-тесты не стартовали из-за отсутствия PostgreSQL/Docker (
localhost:5432 connection refused), а обычный Windowsmanage.py checkограничен отсутствующей системной библиотекой WeasyPrintgobject-2.0-0; обе проверки успешно выполнены Linux PostgreSQL CI.Repository-wide Black/Flake8 локально выявляют существующие нарушения вне diff; изменённые файлы и штатный CI/Lint проходят.
Scope