-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Move to the forked Sobek code #3792
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3792 +/- ##
=======================================
Coverage 71.87% 71.87%
=======================================
Files 291 291
Lines 21274 21274
=======================================
+ Hits 15290 15291 +1
+ Misses 4920 4919 -1
Partials 1064 1064
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 🚀
61cf872
to
e76ab13
Compare
cmd/runtime_options.go
Outdated
@@ -24,7 +24,7 @@ func runtimeOptionFlagSet(includeSysEnv bool) *pflag.FlagSet { | |||
flags.Bool("include-system-env-vars", includeSysEnv, "pass the real system environment variables to the runtime") | |||
flags.String("compatibility-mode", "extended", | |||
`JavaScript compiler compatibility mode, "extended" or "base" or "experimental_enhanced" | |||
base: pure goja - Golang JS VM supporting ES5.1+ | |||
base: pure sobek - Golang JS VM supporting ES5.1+ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
base: pure sobek - Golang JS VM supporting ES5.1+ | |
base: pure Sobek - Golang JS VM supporting ES5.1+ |
Can we have it with a capitalized letter? I see this across multiple lines across this pull request. Consider this suggestion for all of them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not strictly against this, but we do not capitalize it anywhere else as well as far as I can see - and we do not really do it for our other projects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You did it for the first file Dependencies
😅
Btw, I don't think we have other projects with a name independent from k6
. All other projects have names prefixed with k6
or some combination of it like xk6
where it doesn't make sense to capitalize. But in this case, it is a proper name, so I don't see why we shouldn't as it is the correct grammar.
Of course, I expect this only for text and not for code (e.g repo, package names, etc..)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made that lower case as well 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wearing my linguist's cap here 🦖
I have to agree with @codebien here. I would also prefer it if we capitalized Sobek when referring to it in a non-code context (we're displaying information to the user). The reason is that it's used as a "proper noun" here, which in English are always capitalized.
For illustration, the reference to "Golang", three characters away is capitalized for instance.
e76ab13
to
d3497ed
Compare
d3497ed
to
f360312
Compare
Some places weren't applicable as they link to issues or are acknowledging contributions.
f360312
to
93c0c36
Compare
What?
Move to Grafana fork of goja called Sobek - now with the actual code not just aliases
Why?
See #3772
Checklist
make lint
) and all checks pass.make tests
) and all tests pass.Related PR(s)/Issue(s)