Bug Description
Some source files in the repository have missing or misplaced copyright headers. In a few cases, the copyright comment block appears below import statements instead of at the very top of the file. This causes compliance and legal visibility issues.
Reproduction Steps
- Open various TypeScript, JavaScript, or other code files in the repo.
- Observe that in some files, the copyright header appears after one or more import statements (or is missing altogether).
- Files should have the copyright header as the first top-level item, preceding any import statements.
Expected Behavior
- Every
.ts, .js, and relevant source file should have the copyright header (e.g., // Copyright (c) Microsoft Corporation. All rights reserved.) as the very first lines in the file.
- No import (or require) statement should come before the header.
Impact
- Affects license compliance and appropriate attribution in downstream/redistributed code.
Bug Description
Some source files in the repository have missing or misplaced copyright headers. In a few cases, the copyright comment block appears below import statements instead of at the very top of the file. This causes compliance and legal visibility issues.
Reproduction Steps
Expected Behavior
.ts,.js, and relevant source file should have the copyright header (e.g.,// Copyright (c) Microsoft Corporation. All rights reserved.) as the very first lines in the file.Impact