Skip to content

fix: made code samples runnable (#3535) #3596

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

Merged
merged 1 commit into from
May 7, 2024
Merged

Conversation

berezinant
Copy link
Contributor

fixes the problem with runnable code snippets detected in #3535 and described in #3553

@whyoleg
Copy link
Collaborator

whyoleg commented May 7, 2024

Just curious: in future similar issues probably should be detected by ui-showcase screenshot tests, right? Is there a possibility there to check different browsers (Safari, Chrome, Firefox)? I believe in most cases just Chrome will be enough, so I'm just curious.

Copy link
Collaborator

@whyoleg whyoleg left a comment

Choose a reason for hiding this comment

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

LGTM, works at my side

@whyoleg whyoleg mentioned this pull request May 7, 2024
@berezinant
Copy link
Contributor Author

@whyoleg Cases like this are rather hard to prevent only by tests from inside Dokka because of how scripts are included on a page is not totally under our control
But yes, we'll be able to run tests in different browsers and we'll try to cover such cases if possible

@berezinant berezinant merged commit 2d45e27 into master May 7, 2024
@berezinant berezinant deleted the fix-samples-run branch May 7, 2024 14:11
IgnatBeresnev pushed a commit that referenced this pull request May 13, 2024
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