-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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(cli): prepare the string of all model settings and use it in the… #2601
Conversation
…template prepare the string of all model settings and use it in the template, fix one test and add the new one to test this case fix loopbackio#2522
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.
Thank you for the pull request. Please remove unrelated changes to make the patch easier to review.
import {model, property} from '@loopback/repository'; | ||
import {<%= modelBaseClass %>} from '.'; | ||
<% } -%> | ||
import {<%= modelBaseClass %>, model, property} from '@loopback/repository'; |
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.
Please revert unrelated white-space changes.
@@ -1,6 +1,6 @@ | |||
{ | |||
"name": "@loopback/benchmark", | |||
"version": "1.1.12", | |||
"version": "1.1.13", |
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.
Please revert changes in all package-lock files.
I believe we are no longer including LB4 packages in our lock files, see 1d658fb
@yanamg7 , i saw you have another PR #2604, possibly for the same purpose. Does it mean this PR should be closed? Please note that you don't need to open another PR for pushing more changes. Here is a detailed instruction in submitting/modifying a PR: https://loopback.io/doc/en/lb4/submitting_a_pr.html. Thanks. |
Reverted and add new pull request, this one is not relevant already |
In the future, please rebase your existing pull request on top of the new In case you are not familiar with Git history rewriting, you can learn more in our docs: https://loopback.io/doc/en/contrib/code-contrib.html#how-to-rebase-your-branch. The important part is to use |
… template
prepare the string of all model settings and use it in the template, fix one test and add the new
one to test this case
fix #2522
Checklist
👉 Read and sign the CLA (Contributor License Agreement) 👈
npm test
passes on your machinepackages/cli
were updatedexamples/*
were updated