The initial re-working of the docs named the previous version as "legacy", which was relpaced by "1.0.0" as we are now starting our release path for @microsoft/fast-element to "2.0.0", this is a mistake however and should be "1.x" to keep the major versions as the key alignment, 1.x and 2.x should be used respectively without reference to minor or patch versions to avoid confusion.
This may necessitate updates to the docs when new features come out as being available from "2.1.0" onwards for example, a similar pattern is observed in TypeScript docs.
👩💻 Reviewer Notes
This is a simple rename, content has not been changed.
✅ Checklist
General
[ ] I have included a change request file using $ yarn change
[ ] I have added tests for my changes.
[x] I have tested my changes.
[x] I have updated the project documentation to reflect my changes.
[x] I have read the CONTRIBUTING documentation and followed the standards for this project.
Pull Request
📖 Description
The initial re-working of the docs named the previous version as "legacy", which was relpaced by "1.0.0" as we are now starting our release path for
@microsoft/fast-elementto "2.0.0", this is a mistake however and should be "1.x" to keep the major versions as the key alignment, 1.x and 2.x should be used respectively without reference to minor or patch versions to avoid confusion.This may necessitate updates to the docs when new features come out as being available from "2.1.0" onwards for example, a similar pattern is observed in TypeScript docs.
👩💻 Reviewer Notes
This is a simple rename, content has not been changed.
✅ Checklist
General
$ yarn change