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

[Boot] Automatic configuration of controllers in Application #780

Closed
7 tasks done
kjdelisle opened this issue Dec 7, 2017 · 2 comments
Closed
7 tasks done

[Boot] Automatic configuration of controllers in Application #780

kjdelisle opened this issue Dec 7, 2017 · 2 comments
Assignees
Labels
Milestone

Comments

@kjdelisle
Copy link
Contributor

kjdelisle commented Dec 7, 2017

Story

As a LoopBack 4 user, I would like all of the controller files I place (or generate!) in ./src/controllers to automatically be associated with my Application so that I don't have to type app.controller(...) over and over again.

Acceptance Criteria

  • Must read all files of the format *.controller.js from the controllers directory
  • Must associate all of the controllers exported classes with the application using the .controller function.
    • Take each exported class from the *.controller.js file (subject to change based on user feedback)
  • There should be a blog post informing users that this is now live (once this change has been released!), and explain how it works.
  • Docs on loopback.io
  • Refactor/update example code (loopback4-example-getting-started)
  • Update app template(s) in CLI to use @loopback/boot

Notes

  • Extensibility is out of scope; it does not need to accommodate anything beyond the current story for Controllers.
@jonathan-casarrubias
Copy link

+1

@kjdelisle kjdelisle added the MVP label Dec 7, 2017
@shimks shimks changed the title Automatic configuration of controllers in Application [Boot] Automatic configuration of controllers in Application Dec 8, 2017
@bajtos bajtos mentioned this issue Dec 12, 2017
10 tasks
@virkt25 virkt25 self-assigned this Dec 18, 2017
@b-admike b-admike added this to the Sprint 52 milestone Dec 27, 2017
@dhmlau dhmlau modified the milestones: Sprint 52, Sprint 53 Jan 9, 2018
@virkt25 virkt25 mentioned this issue Jan 12, 2018
6 tasks
@kjdelisle kjdelisle modified the milestones: Sprint 53, Sprint 54 Jan 23, 2018
@kjdelisle kjdelisle removed this from the Sprint 54 milestone Jan 24, 2018
@kjdelisle kjdelisle added this to the February 2018 milestone Jan 30, 2018
@virkt25
Copy link
Contributor

virkt25 commented Feb 28, 2018

Done :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants