Repository navigation
Conversation
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
1 participant
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.
What change does this PR introduce?
Follow-up to #379:
utils/identity-cell-resource.jsre-exportsbuildIdentityStubfrom@fleetbase/fleetops-data/utils/identity-stubinstead of defining it, so every extension builds identity stubs the same way.resolveIdentityCellResourcestays here. No call site changes.Why was this change needed?
The stub builder moved to the shared package (fleetops-data follow-up to #86) so Storefront can use it; this removes the duplicate.
Other information
Depends on that fleetops-data PR being released; until then the import resolves only through the workspace link. The descriptor, wrapper and identity-cell suites are unaffected (the same filtered run as on #379).