-
Notifications
You must be signed in to change notification settings - Fork 35
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
[Fix] Keep translation QTI ID the same #4206
base: develop
Are you sure you want to change the base?
Conversation
Front-end summary Node 18
|
$this->getQtiIdentifierSetter($resource)->set([ | ||
AbstractQtiIdentifierSetter::OPTION_RESOURCE => $resource, | ||
AbstractQtiIdentifierSetter::OPTION_IDENTIFIER => $uniqueIdentifier, | ||
]); | ||
|
||
if ($this->featureFlagChecker->isEnabled('FEATURE_FLAG_UNIQUE_NUMERIC_QTI_IDENTIFIER')) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shpran I wonder if we really need this if here now? If we are creating a translation, it may be useful to for them to have always the same TaoOntology::PROPERTY_UNIQUE_IDENTIFIER
?
I know this is only needed for HKDir for the moment, but I do not see why restrict is as default behavior.
- I know it was previous rule in place, but better thinking about it, we may remove this condition.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If for us it's not a problem if we are going to set this property every time - I will remove this condition 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done: 7f03156
Also did for:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!
- New code is covered by tests (if applicable)
- Tests are running successfully (old and new ones) on my local machine (if applicable)
- New code is respecting code style rules
- New code is respecting best practices
- New code is not subject to concurrency issues (if applicable)
- Feature is working correctly on my local machine (if applicable)
- Acceptance criteria are respected
- Pull request title and description are meaningful
Version
There are 0 BREAKING CHANGE, 0 feature, 1 fix |
AUT-3772
Changes
How to test
FEATURE_FLAG_UNIQUE_NUMERIC_QTI_IDENTIFIER
feature flagFEATURE_FLAG_TRANSLATION_ENABLED
feature flagReady for translation
Companion PRs