Skip to content
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

fix(sequelize): parse JSON columns to objects for mysql dialect #10285

Merged
merged 5 commits into from
Apr 9, 2024

Conversation

KalleV
Copy link
Contributor

@KalleV KalleV commented Jan 7, 2024

By parsing the values to JSON objects, provide backward compatibility for JSON and Array entity properties when using dialects like MySQL, MariaDB, or SQLite.

Fixes: #9629
Fixes: #9598

Checklist

  • DCO (Developer Certificate of Origin) signed in all commits
  • npm test passes on your machine
  • New tests added or existing tests modified to cover all changes
  • Code conforms with the style guide
  • API Documentation in code was updated
  • Documentation in /docs/site was updated
  • Affected artifact templates in packages/cli were updated
  • Affected example projects in examples/* were updated

👉 Check out how to submit a PR 👈

@KalleV KalleV marked this pull request as ready for review January 7, 2024 18:51
@KalleV KalleV requested a review from samarpanB as a code owner January 7, 2024 18:51
@coveralls
Copy link

coveralls commented Jan 7, 2024

Pull Request Test Coverage Report for Build 8590810023

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 55.371%

Totals Coverage Status
Change from base Build 8564057942: 0.0%
Covered Lines: 9563
Relevant Lines: 12457

💛 - Coveralls

@KalleV KalleV force-pushed the KalleV-fix-json-data-types-mysql branch from 98a5a9d to 8a3c326 Compare January 9, 2024 20:43
@KalleV KalleV changed the title fix(sequelize): parse JSON columns to objects for non-Postgres dialects fix(sequelize): parse JSON columns to objects for mysql dialect Jan 9, 2024
Copy link
Contributor

@shubhamp-sf shubhamp-sf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@samarpanB
Copy link
Contributor

@KalleV This PR is good to be merged now. Can you please rebase this PR ?

Signed-off-by: KalleV <kvirtaneva@gmail.com>
Signed-off-by: KalleV <kvirtaneva@gmail.com>
Signed-off-by: KalleV <kvirtaneva@gmail.com>
Signed-off-by: KalleV <kvirtaneva@gmail.com>

chore: merge conflicts

Signed-off-by: KalleV <kvirtaneva@gmail.com>

chore: refactor type import

Signed-off-by: KalleV <kvirtaneva@gmail.com>

chore: skip db2 in parseJsonColumn test

Signed-off-by: KalleV <kvirtaneva@gmail.com>

chore: fix test case

Signed-off-by: KalleV <kvirtaneva@gmail.com>

chore: empty commit for CI

Signed-off-by: KalleV <kvirtaneva@gmail.com>
@KalleV KalleV force-pushed the KalleV-fix-json-data-types-mysql branch from e7317a4 to bf20d64 Compare April 7, 2024 18:32
@KalleV
Copy link
Contributor Author

KalleV commented Apr 7, 2024

@samarpanB Thanks! I fixed the rebase merge conflicts.

@dhmlau dhmlau merged commit 5839f5e into loopbackio:master Apr 9, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants