Modernize source file headers #1144
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
About adding my name to the headers: That's something that lately came up in a correspondence between a corporate user of long.js and me, since "The XY Contributors" was too vague for their legal department as that's not a legal entity I suppose. Now I know that a lot of open source projects do it that other way, but I guess it's always better to be safe than sorry. |
MaxGraey
approved these changes
Mar 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Source files were still using some hacky comments to be compatible with tsdoc, which turned out we don't use/need. So this PR updates the comments to a more friendly format while also including license headers.
src/index.ts@licensetag with the SPDX identifier