Conversation
added 28 commits
January 15, 2023 16:53
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
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.
As there is a product at Unbabel that uses micro frontends, I decided to go for a npm workspaces approach, decoupling possible shared/common modules. In this case, I only decoupled the API part, but could also be made for base UI components.
Also, the app is running a late vue 2 version, meaning that allows the use of the composition API, which I used.
Things I highlight:
useTranscriptionsStorecomposable that manages transcriptions' module state.useTranscriptionsServicecomposable that handles app and API "connection". Works as a translation layer, If anything on the API changes, we'll only need to change it here.TranscriptionReadModelclass. This is a pattern that I personally like. It works like a helper for the View Model, with only readonly properties. It allows us to "lock" specific component prop types while also being the single source of truth for all thetranscription's properties display.As I don't have much free time, I tried to be pragmatic. Some improvements that could be made: