-
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
Document how is the CLI generator discovering models and repositories in the project #1085
Comments
@bajtos Please update the issue with the appropriate acceptance criteria |
@shimks done. |
Rejecting based on wanting to improving the UX for this type of controller generation and wanting to leverage EDIT: clarifying that we're rejecting this task from estimation |
I disagree. Right now, people using Leveraging |
Based on the discussion brought up in estimation, it's been expressed that it feels more correct to explain how the models and repositories are discovered with how The ideal plan is to improve the documentation on trying to use all LB4 CLI tools to build a functioning lb4 project (in lieu of For right now, just adding links to concepts like models and repositories in the |
@shimks here is the (user) story I'd like to get addressed by this issue for DP3: As a developer building a new LB4 app, I ran |
My take of eliminating the confusion would be:
Thought? |
I am fine with describing the naming convention in our docs, as you proposed @jannyHou. BUT: IMO, it would not occur to most people (including) myself that we need to look into README, I wouldn't be sure where to find it. Do you mean the output of I still think the CLI should show some hint to the user to make it easier for them to find the documentation. At least when the CLI could not find any artifacts, it can bail out with an error message along the following lines:
|
See #727 (comment):
Acceptance criteria
@loopback/boot
does? Are we building the class names from file names? Are there any filters (e.g. does a repository class name have to includeRepository
suffix)? Etc.The text was updated successfully, but these errors were encountered: