Resolve "Fix pipeline configuration input resetting value while typing"
What does this MR do?
This MR fixes the pipeline configuration input resetting it's value when the user typed quickly.
This was caused because the path was being set back to an older value once fetchPipelineConfigurationFileExists resolved.
Setup & Testing
- Enable the development feature flag in rails console:
Feature.enable(:ff_custom_compliance_frameworks) - Navigate to a group's general settings
[GDK_HOST]/groups/gitlab-org/-/edit#js-compliance-frameworks-settings - Add a compliance framework
Screenshots (strongly suggested)
| Before | After |
|---|---|
 |
 |
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because its behind a development feature flag.
-
- [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
-
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #321978 (closed)
Edited by Jiaan Louw