Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: export variables for better consumption from the outside #27189

Merged
merged 1 commit into from
Dec 2, 2024

Conversation

ffMathy
Copy link
Contributor

@ffMathy ffMathy commented Dec 2, 2024

This will allow others to consume how far Deno is from a compatibility-perspective.

Here's a discussion: #26745

From that, I made this site: https://ffmathy.github.io/is-deno-compatible-yet/

But it is showing the wrong calculations. Exposing these fields would make it easy for me to "piggyback" on the right numbers.

This will allow others to consume how far Deno is from a compatibility-perspective.

Signed-off-by: Mathias Lykkegaard Lorenzen <[email protected]>
@CLAassistant
Copy link

CLAassistant commented Dec 2, 2024

CLA assistant check
All committers have signed the CLA.

Copy link
Member

@kt3k kt3k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

BTW we are planning to make these changes in some future. In that case, getDenoTests becomes an async function.

@ffMathy
Copy link
Contributor Author

ffMathy commented Dec 2, 2024

@kt3k sounds fine to me. Although this will essentially make these functions a "public API", I am fine with it breaking. We could maybe just keep it "as-is".

@kt3k kt3k merged commit f9a6cc3 into denoland:main Dec 2, 2024
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants