-
Notifications
You must be signed in to change notification settings - Fork 20
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
feat: Use Common db model types in frontend #291
Conversation
be305a6
to
90bcdaa
Compare
731d855
to
1c372bd
Compare
58c75da
to
e7a9767
Compare
@@ -66,7 +66,38 @@ pub struct Dimension { | |||
pub position: i32, | |||
} | |||
|
|||
#[derive(Serialize, Clone)] | |||
#[derive(Debug, Clone, Serialize, Deserialize)] |
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 dont think these types should be in models , can we use some other file for these types which are not related to
the db table
@@ -155,13 +158,51 @@ impl From<HashMap<String, String>> for QueryMap { | |||
} | |||
} | |||
|
|||
#[derive(Debug, Clone)] | |||
#[derive(Debug, Clone, PartialEq)] | |||
pub struct PaginationParams { |
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.
these types shouldn't be in models file
e7a9767
to
2b2b7e4
Compare
bd5c3d8
to
576c6b7
Compare
576c6b7
to
2937a97
Compare
The base branch was changed.
Problem
Types redefined in
frontend
crateSolution
Remove the repeated definitions from
frontend
crate and re-use types defined insuperposition_types
Continuation for this PR