-
-
Notifications
You must be signed in to change notification settings - Fork 305
feat: User preferences storage & admin: sorted billing plans by populality #3266
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
Draft
JanCizmar
wants to merge
2
commits into
main
Choose a base branch
from
jancizmar/fe-storage-and-billing-plans-sorting
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
10 changes: 10 additions & 0 deletions
10
backend/data/src/main/kotlin/io/tolgee/dtos/request/UserStorageResponse.kt
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
package io.tolgee.dtos.request | ||
|
||
import com.fasterxml.jackson.annotation.JsonIgnoreProperties | ||
import io.swagger.v3.oas.annotations.media.Schema | ||
|
||
@JsonIgnoreProperties(ignoreUnknown = true) | ||
data class UserStorageResponse( | ||
@field:Schema(description = "The data stored for the field") | ||
var data: Any? = null, | ||
) |
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
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
import { useApiMutation, useApiQuery } from 'tg.service/http/useQueryApi'; | ||
import { UseQueryResult } from 'react-query'; | ||
|
||
/** | ||
* Hook returning the methods to get an update user preference storage. | ||
* The data is stored on the server as a JSONB field. | ||
* | ||
* Use it anywhere you need to store some not-big data for the specific user. | ||
*/ | ||
export function useUserPreferenceStorage(fieldName: string) { | ||
const loadable = useApiQuery({ | ||
url: '/v2/user-preferences/storage/{fieldName}', | ||
method: 'get', | ||
path: { fieldName }, | ||
}) as UseQueryResult<{ data: Record<number, number> }>; | ||
|
||
const mutation = useApiMutation({ | ||
url: '/v2/user-preferences/storage/{fieldName}', | ||
method: 'put', | ||
}); | ||
|
||
return { | ||
loadable, | ||
update: (value: Record<string, any>) => { | ||
mutation.mutate({ | ||
path: { fieldName }, | ||
content: { | ||
'application/json': value, | ||
}, | ||
}); | ||
}, | ||
}; | ||
} |
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🛠️ Refactor suggestion | 🟠 Major
🧩 Analysis chain
Avoid lost updates on storageJson (concurrent writes overwrite each other).
This read-modify-write of the whole JSON map can drop parallel changes. Add optimistic locking (version) and wrap in one transaction; or patch the JSONB in-place.
Diff (transactional + no-op when unchanged):
Alternative (safer under concurrency): a repository UPDATE using jsonb_set to upsert/remove a single key atomically, avoiding map rewrites. I can draft this if you want.
To verify optimistic locking support:
🏁 Script executed:
Length of output: 26
🏁 Script executed:
Length of output: 1357
Add optimistic locking or atomic JSONB updates to prevent lost updates
UserPreferences has no @Version field, so concurrent calls to setStorageJsonField will overwrite each other. Wrap the method in @transactional and add a version property (optimistic locking), or switch to an UPDATE using jsonb_set to patch a single key. Example refactor:
🤖 Prompt for AI Agents