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

Blazor 3.0 Roadmap #8177

Closed
rynowak opened this issue Mar 4, 2019 · 2 comments

Comments

@rynowak
Copy link
Member

commented Mar 4, 2019

This is a tracking item for the overall Blazor features in .NET Core 3.0

Items are arranged by milestone.

DESIGN: items mean that the design work will occur in that milestone - the actual product work will generally happen in the next milestone.

Preview 3

  • #6351 - Updates to Event Handling and Bind
  • #4057 - Tooling for .razor
  • #4054 - Startup Experience
  • #5464 - Prerendering
  • #5460 - Forms and Validation
  • #6353 - Component lifecycle and events

Preview 4 / VS 16.1 preview 1

Preview 4 is a long milestone and is aligned with a VS release. Therefore we are trying to pack in as much as possible related to tooling and language

  • #4048 - DESIGN: Auth
  • #6349 - DESIGN: multi-project static content
  • #5545 - DESIGN: Control over event propagation and default actions
  • #7573 - Handle reconnection to same server
  • #5110 - Replacement for @helper
  • #6392 - Define template experience for Component-only RCL
  • #5577 - Components are based on @using instead of @addTagHelper
  • #5106 - Use Root Namespace from project file for components
  • #6374 - _Imports.razor
  • #7311 - Use Shared-Framework-allowed MessagePack serializer
  • #TBD - Follow Up: .razor, templates and tooling
  • #TBD - Follow Up: SignalR connection problems and troubleshooting
  • #5092 - C#8 support in Razor

Preview 5

Preview 5 is a relatively short milestone and we don't expect to fix things during this time that require tooling changes

Preview 6

  • #10393 - Support @attribute directive
  • #6364 - Directive attributes
  • #8205 - Use System.Text.Json in Components/JSInterop
  • #8232 - Support key to guarantee preservation of element/component instances
  • #5629 - Make SignalR Service usage an aspect of deployment, not source code
  • #6361 - Support @code
  • #6349 - IMPLEMENT: multi-project static content
  • #4048 - IMPLEMENT: Auth

Preview 7

Preview 7 has a small number of actual deliverable features... we're investing the most time in some of ongoing 3.0 efforts listed in the 3.0 Tracking section

  • #5071 - Splat operator for attributes
  • #8204 - Async diffing

Preview 8

  • #9386 - Globalization support
  • #7536 - RCL template offers choice between Components or MVC
  • #8825 - Update visibility of component parameters
  • #9860 - Make component binding case-sensitive
  • #9565 - Security review for server-side Blazor

Preview 9

We have planned no any feature work in this milestone and we will be focusing on bug fixes only.
Some other things which we may have to handle here are potential follow-ups from security and API reviews.

  • #4050 - Blazor API review

3.0 Tracking

  • #10472 - Server-side Blazor in production
  • #10449 - Server-side Blazor E2E performance and capacity testing

3.1

  • #7268 - [Blazor] Add ability to pass @typeparam down to child components
  • #8613 - Follow Up: Error handling improvements
  • #5545 - IMPLEMENT: Control over event propagation and default actions
  • #5487 - Components support partial classes

TBD

Backlog

Items here are arranged in rough priority order.

  • #4065 - Unify Razor editor initialization with closed file infrastructure (blocks EnC, Refactoring, Partial Classes)
  • #7268 - DESIGN: Child Components with strong typing
  • #7268 - IMPLEMENT: Child Components with strong typing
  • #6348 - DESIGN: Enable Views/Pages to use component as elements
  • #6348 - IMPLEMENT: Enable Views/Pages to use component as elements
  • #8183 - Generate event handler methods in VS
  • #8214 - Component Islands
  • #5471 - Localization support
  • #6356 - Components VSCode support
  • #5490 - Components VS4Mac support
  • #5562 - reconnection to a different server
  • #6358 - Automated eviction for circuits
  • #4052 - Performance infrastructure and hello world perf test
  • Unit Testing
  • Scaffolding

@rynowak rynowak added this to the 3.0.0 milestone Mar 4, 2019

@rynowak rynowak added this to Triage in Blazor via automation Mar 4, 2019

@rynowak rynowak moved this from Triage to Design in Blazor Mar 4, 2019

@aspnet aspnet locked as resolved and limited conversation to collaborators Mar 4, 2019

@rynowak

This comment has been minimized.

Copy link
Member Author

commented Mar 4, 2019

Locking this because it's our high-level planning and status issue. Feel free to use other issues to discuss or give feedback.

@rynowak rynowak moved this from Design to Tracking in Blazor Mar 16, 2019

@danroth27 danroth27 changed the title Razor Components Roadmap Blazor Roadmap May 3, 2019

@mkArtakMSFT mkArtakMSFT added area-blazor epic and removed area-mvc labels May 17, 2019

@danroth27

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

Closing as we are done with feature work for 3.0! Wohoo!

@danroth27 danroth27 closed this Sep 3, 2019

Blazor automation moved this from Tracking to Done Sep 3, 2019

@danroth27 danroth27 changed the title Blazor Roadmap Blazor 3.0 Roadmap Sep 6, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
3 participants
You can’t perform that action at this time.