[18.0][ADD] project_sequence_type: per-type project sequence#1737
Open
dnplkndll wants to merge 1 commit into
Open
[18.0][ADD] project_sequence_type: per-type project sequence#1737dnplkndll wants to merge 1 commit into
dnplkndll wants to merge 1 commit into
Conversation
OCA-git-bot
added
series:18.0
mod:project_sequence_type
Glue module (auto-installing with project_sequence + project_type) that lets each project.type point at its own ir.sequence. Projects of that type take their sequence_code from it; types with no sequence, and projects with no type, keep using the global project.sequence.
dnplkndll
force-pushed
the
18.0-add-project_sequence_type
branch
from
1c8150e to
5aa91c7
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
2 participants
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.
Back-port of
project_sequence_typefrom 19.0 (#1736).New glue module bridging
project_sequenceandproject_typeso each projecttype can have its own sequence — answering the recurring "I need a different
sequence per project type" request. It adds a
sequence_id(ir.sequence) fieldon
project.type; projects of a type take theirsequence_codefrom thatsequence, while types with no sequence — and projects with no type — keep using
the global
project.sequence.auto_install, so it activates only when bothbase modules are present.
Non-mechanical adaptations worth flagging
project.project.create()pre-fillssequence_codefrom the type's sequencebefore
super(), mirroringproject_sequence's own "only when the key isabsent" guard — preserving its default-name logic and never overriding an
explicit
sequence_code. (Identical to 19.0; the 18.0 base modules share thesame create semantics and view structure.)