Skip to content
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.

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

[#60666] User can't save lifecycle modal if project is invalid #17647

Merged
Merged
Changes from 1 commit
Commits
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
Prev Previous commit
Next Next commit
Fix typo
dombesz committed Jan 23, 2025
commit 22aca58c3921c8245e8d25a5b7c2c91fcd71e484
4 changes: 2 additions & 2 deletions app/models/project.rb
Original file line number Diff line number Diff line change
@@ -110,8 +110,8 @@ class Project < ApplicationRecord
# Providing a custom context while creating the project, will not execute the callbacks on the
# `:create` or `:update` contexts, meaning the identifier will not get initialised.
# In order to initialise the identifier, the `default_validation_context` (`:create`, or `:update`)
# should be included when validating via the `:saving_custom_fields`. This way ever create or update
# callback will also be executed alongside the `:saving_custom_fields` callbacks.
# should be included when validating via the `:saving_custom_fields`. This way every create
# or update callback will also be executed alongside the `:saving_custom_fields` callbacks.
# This problem does not affect the contextless callbacks, they are always executed.

def validation_context