Closed jannyHou closed 3 years ago
(Not sure is it a good idea to do them in one story, or should I create two?)
Let's create two stories please.
This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS
file at the top-level of this repository. This issue will be closed within 30 days of being stale.
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS
file at the top-level of this repository.
connect to https://github.com/strongloop/loopback-next/issues/2036 This is a follow-up story of PR https://github.com/strongloop/loopback-next/pull/3667. As a quick fix, that PR fixes the controller generator by adding a new prompt
isIdOmitted
, and creating the corresponding controller class differently.There are two more improvements which need more time to address, so I open a new issue here.
Suggestion
Update the controller class in
@loopback/rest-crud
to reflect the id property's configuration.Acceptance criteria
@loopback/rest-crud
package, so that it generates the correct schema for id property. See discussion and discussion