You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rule engine operates on tracks, but some metadata properties belong to releases. How can we unify releases and tracks?
Protocol: Some matchers only match entire releases; other matchers only match entire tracks. Running a release action on a track modifies its entire release.
This is almost what happens right now, except when we modify a release variable on single track, it only updates the entire release if it is the first track.
The rules engine could be rearchitected to take into account this distinction as well.
The text was updated successfully, but these errors were encountered:
The rule engine operates on tracks, but some metadata properties belong to releases. How can we unify releases and tracks?
Protocol: Some matchers only match entire releases; other matchers only match entire tracks. Running a release action on a track modifies its entire release.
This is almost what happens right now, except when we modify a release variable on single track, it only updates the entire release if it is the first track.
The rules engine could be rearchitected to take into account this distinction as well.
The text was updated successfully, but these errors were encountered: