-
Notifications
You must be signed in to change notification settings - Fork 14
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
Import feature flag validation API and related UI changes, validation table #1798
Conversation
backend/packages/Upgrade/src/api/services/FeatureFlagService.ts
Outdated
Show resolved
Hide resolved
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.
I've looked at the backend. I had a couple suggestions.
backend/packages/Upgrade/src/api/services/FeatureFlagService.ts
Outdated
Show resolved
Hide resolved
@bcb37 just a clarification, does the warning state only come if any public subsegments of private segments are not present? |
...hboard/feature-flags/modals/import-feature-flag-modal/import-feature-flag-modal.component.ts
Outdated
Show resolved
Hide resolved
That's my understanding, yes. |
(await this.featureFlagsDataService.validateFeatureFlag(files).toPromise()) as ValidateFeatureFlagError[] | ||
).filter((data) => data.compatibilityType != null) || []; | ||
this.importFileErrorsDataSource.data = this.importFileErrors; | ||
this.featureFlagsService.setIsLoadingImportFeatureFlag(false); |
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.
It looks like Observable<Object>.toPromise()
is deprecated and is replaced with firstValueFrom
and lastValueFrom
. Could you update this?
@Yagnik56 It looks like importing with dragging and dropping a file is not implemented yet. |
It seems like the compatibility type is always "Incompatible" even if I import the valid one (which I just exported). |
@zackcl Did you change the KEY after you exported the FF? duplicate key will give you an incompatible message... |
@Yagnik56 No, I tried importing when there are no flags defined. I exported a feature flag, and then deleted the existing one, and then imported the exported one. Can you also try this yourself? |
@zackcl The export structure is not perfect, there were some property names mismatched, this is discussed in export PR. Its merge is remaining that's why exported FeatrueFlags shows error while importing |
…ion-rename-list-to-segment Rename 'list' to 'segment' in FeatureFlagListValidator and related files
backend/packages/Upgrade/src/api/controllers/validators/FeatureFlagImportValidator.ts
Outdated
Show resolved
Hide resolved
* solve feature flag throwing error update * Removed unused properties from featureFlags related interfaces --------- Co-authored-by: RidhamShah <[email protected]>
@VivekFitkariwala will check latest |
This PR introduces several new features and improvements:
Validation Enhancements:
Bug Fixes:
Merged PRs:
This PR is now ready for review