Tracking issue for yew 0.20

[WorldSEnder]

Yew 0.20 will focus on making Yew applications SEO friendly and pre-rendering the page with server-side rendering (SSR). We're also ironing out our function component support, with hooks that should be familiar if you're coming from React (this part is for the most part done on the master branch).

The plan towards yew 0.20

• Allow generating state on server side and subsequently consume it on the client in SSR Send states created during SSR alongside SSR artifact to be used with client-side rendering hydration #2649

• Immutable Introduce immutable string, array and map #2563

• Remove ref for components: Components should not have a node ref #2505 + Remove component NodeRef #2783

• Improve testing of components. Could be accomplished by

  • Document at least one possible way to reuse an existing framework for E2E testing Develop E2E Tests #196
  • Rework the exposed yew::tests modules Rewrite testing code to a TestRunner managing dom context #2679 which could also address Add support for shallow rendering #1412
  • Experiments were made, and Add ability to update app props #2951 adds some public API that could allow most of the testing to be driven externally. Further test development will be done in an external repo, too.

• Fix event types for some uncommon event types onsubmit should be a SubmitEvent, not a FocusEvent #2691

• Decide on prop vs attribute usage Select element last element cant be set programatically #2530, Bind to properties instead of attributes by default  #1322

  • Document the syntax for setting properties in Add syntax to bind to properties instead of attributes #2819

• Decide on API breakage needed for Can't access old props in changed() to compare to new props #2724

• Update yew-agent to Worker v2 Agent v2 #2773

• Additional documentation

  • Document literal escaping behaviours related to xss prevention  #2682
  • Couple of broken links on the yew crates page. #2789
  • Document the usage of tracing #2818
  • Include updated documentation on best practices related to making requests or doing other asynchronous operations inside Yew components #2837
  • Calling hooks in a fn without #[hook] has terrible diagnostics #2614
  • Hooks do not work inside html! #2612
  • Negative literals don't work #2574
  • Suspension busy polling instead of waiting #2571
  • Tips about component communication #2197
  • Document anti-pattrens regarding props #1843

Minor issues and stretch

• Document and battle-test SSR edgecases, i.e. Hydration failure when providing a <table> without <tbody> #2684
• Nightly-only features tracked in Add a nightly feature flag to use nightly features #2681
• Performance of the html macro Investigate performance of html macro #2520 and minor issues Generic tuple type panicks html macro in the closing tag #2225, Emit Warning when not using shorthand syntax #1979
• Homepage Have a better home page #2393 and slogan Suggestion for a new slogan #2378
• Prop order might be unintuitive Define prop execution order #1634
• Allow empty dynamic tags Reconcile difference between dynamic tags, literal tags, and manual creation #1269

[ranile]

I've removed imperative_ref from 0.20. Also see: #2783 (review)

[spanishpear]

should yew_agent upgrading to gloo_worker 0.2.1 be on the roadmap for 0.20? I'm not sure if that's the scope of #2773 , or something else

[futursolo]

should yew_agent upgrading to gloo_worker 0.2.1 be on the roadmap for 0.20? I'm not sure if that's the scope of #2773 , or something else

#2773 was the effort to upgrade to gloo-worker 0.2 (Worker v2) and revisit the yew-agent API in general which should come before Yew 0.20 unless it is not accepted.
However, I felt that the functional agent API included in #2773 can also be included in gloo-worker and benefit a bigger community so I have created ranile/gloo#251 for consideration.
I am waiting for the maintainers of gloo to reach a decision on ranile/gloo#251 before proceeding with #2773.

I have updated the tracking issue to reflect this.