feat: enhance StellarLend documentation, setup guide, and developer workflow#413
Open
Tobiloba0 wants to merge 1 commit into
Open
feat: enhance StellarLend documentation, setup guide, and developer workflow#413Tobiloba0 wants to merge 1 commit into
Tobiloba0 wants to merge 1 commit into
Conversation
|
@Tobiloba0 is attempting to deploy a commit to the smartdevs17's projects Team on Vercel. A member of the Team first needs to authorize it. |
Author
|
Vercel deployment requires authorization from maintainer. |
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.
What Changed
next: NextFunctionparameters to Express handlers in:buildHealthFactorMonitorand updating its usage.subscribe_analytics/unsubscribe_analytics) and corresponding server messages.Why
next(error)without declaring thenextparameter, and WebSocket client message types lacked analytics subscription messages.fix/issue-358. The changes fix the root causes so the API compiles cleanly and correctly types analytics WS messages.Testing
cd api && npm run buildandnpm --workspaces run build --if-present(both succeeded)Closes #358