feat: expose __unenv__ flag for unenv classes and functions
#125
Conversation
This file contains 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
pi0
commented
Aug 8, 2023
| @@ -1 +1,5 @@ | |||
| export default {}; | |||
| export default Object.freeze( | |||
There was a problem hiding this comment.
Note: freezing is not related to this PR but quickly included as fix
This was referenced Aug 8, 2023
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.
🔗 Linked issue
❓ Type of change
📚 Description
it is commonly required to identify if something is coming from unenv or not specially for classes and mocked objects.
This PR adds
__unenv__property to class (instances) and functions to identify.Note: Since we were already using
req.__unenv__for another purpose (#72), the type forIncommingMessageandReadableclasses is unknown/object.📝 Checklist