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

Snippet on why hot reload is awesome #1002

Closed
emmanuelbernard opened this issue Feb 22, 2019 · 1 comment
Closed

Snippet on why hot reload is awesome #1002

emmanuelbernard opened this issue Feb 22, 2019 · 1 comment
Assignees
Milestone

Comments

@emmanuelbernard
Copy link
Member

do we want to call it hot reload or live reload?

Explain:

  • how it works
    • detect class and resources changes
    • on refresh, reload the entire app
    • super fast because Protean is super fast optimized
  • what is the dev flow and how to best use it
    • UI down to DB driven dev
    • complementary to (unit) tests
@emmanuelbernard emmanuelbernard changed the title Why hot reload is awesome Snippet on Why hot reload is awesome Feb 22, 2019
@emmanuelbernard emmanuelbernard changed the title Snippet on Why hot reload is awesome Snippet on why hot reload is awesome Feb 22, 2019
@stuartwdouglas stuartwdouglas self-assigned this Feb 22, 2019
@jclingan
Copy link

jclingan commented Feb 24, 2019

We need to nail down if we want to call it "hot reload" or "live reload" since other content (web site, presentations) will need to use the term. Looking at the spring.io web site, live reload seems to be used more, but hot reload is also used by boot developers in stack overflow. I'm neutral on it since both are well understood, so I'll let those that implemented the feature decide :-) The analyst deck has "live reload". In addition, the log output for the maven plugin is "hot replace", so it will need to be updated to align with the decision. Ditto for the getting started guide, which also uses "hot deployment".

stuartwdouglas added a commit that referenced this issue Feb 28, 2019
@gsmet gsmet added this to the 0.10.0 milestone Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants