-
-
Notifications
You must be signed in to change notification settings - Fork 242
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
Ensure compatibility with ruby --enable-frozen-string-literal
#508
Ensure compatibility with ruby --enable-frozen-string-literal
#508
Conversation
Ref: https://bugs.ruby-lang.org/issues/20205 `json-schema` is used by the `rbs` gem, which is tested as part of the `ruby-core` CI, and it's failing with frozen string literals are enabled by default.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #508 +/- ##
=======================================
Coverage 90.08% 90.08%
=======================================
Files 76 76
Lines 1584 1584
=======================================
Hits 1427 1427
Misses 157 157 ☔ View full report in Codecov by Sentry. |
Thanks for the patch @casperisfine |
Thanks for the extremely timely merge :) |
As a maintainer I know it's annoying to be asked for a release, but in this case I arrived here because I'm trying to get So I'd owe you one if you could cut a release soon 🙏 |
Ref: https://bugs.ruby-lang.org/issues/20205 Ref: voxpupuli/json-schema#508 Since `rbs` is tested as part of ruby-core CI, it needs to be compatible with the `--enable-frozen-string-literal` option.
already on it :) |
😻 |
Ref: https://bugs.ruby-lang.org/issues/20205 Ref: voxpupuli/json-schema#508 Since `rbs` is tested as part of ruby-core CI, it needs to be compatible with the `--enable-frozen-string-literal` option.
considering #507 resolved too |
Ref: https://bugs.ruby-lang.org/issues/20205 Ref: voxpupuli/json-schema#508 Since `typeprof` is tested as part of ruby-core CI, it needs to be compatible with the `--enable-frozen-string-literal` option.
Ref: https://bugs.ruby-lang.org/issues/20205 Ref: voxpupuli/json-schema#508 Since `typeprof` is tested as part of ruby-core CI, it needs to be compatible with the `--enable-frozen-string-literal` option.
Ref: https://bugs.ruby-lang.org/issues/20205 Ref: voxpupuli/json-schema#508 Since `typeprof` is tested as part of ruby-core CI, it needs to be compatible with the `--enable-frozen-string-literal` option.
Ref: https://bugs.ruby-lang.org/issues/20205 Ref: voxpupuli/json-schema#508 Since `typeprof` is tested as part of ruby-core CI, it needs to be compatible with the `--enable-frozen-string-literal` option.
Ref: https://bugs.ruby-lang.org/issues/20205 Ref: voxpupuli/json-schema#508 Since `typeprof` is tested as part of ruby-core CI, it needs to be compatible with the `--enable-frozen-string-literal` option.
Ref: https://bugs.ruby-lang.org/issues/20205 Ref: voxpupuli/json-schema#508 Since `typeprof` is tested as part of ruby-core CI, it needs to be compatible with the `--enable-frozen-string-literal` option.
Ref: https://bugs.ruby-lang.org/issues/20205 Ref: voxpupuli/json-schema#508 Since `rbs` is tested as part of ruby-core CI, it needs to be compatible with the `--enable-frozen-string-literal` option.
Ref: https://bugs.ruby-lang.org/issues/20205 Ref: voxpupuli/json-schema#508 Since `typeprof` is tested as part of ruby-core CI, it needs to be compatible with the `--enable-frozen-string-literal` option.
They've fixed frozen-string-literal issue. Apparently it needed a different maintainer to approve identical changes proposed one more time. voxpupuli/json-schema#507 voxpupuli/json-schema#508 Co-authored-by: Szymon Fiedler <[email protected]>
Ref: https://bugs.ruby-lang.org/issues/20205
json-schema
is used by therbs
gem, which is tested as part of theruby-core
CI, and it's failing with frozen string literals are enabled by default.