Skip to content

Regenerate reference packages in SBRP #3459

Closed
@MichaelSimons

Description

@MichaelSimons

Now that the work to improve the SBRP generate tooling is completed, all reference packages should be regenerated. This will provide the following benefits:

  1. It will improve the UX for adding new packages. When a new package is generated the default is to generate the packages for its dependencies. It is common for dependencies to already exist but they would be regenerated. When existing packages are regenerated, there are a lot of diffs. This creates a lot of "noise" in PRs and can be a source of confusion. If all reference packages were regenerated, this noise would be eliminated.
  2. The new generated code is better. The new generated source is more accurate and formatted better. Additionally the project files are much simpler.
  3. This will help test the new generator and help surface any issues it has.

Metadata

Metadata

Assignees

Labels

area-sbrpSource build reference packages

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions