rbs_parser
Packagist
rbs_parser | Packagist | |
---|---|---|
3 | 61 | |
28 | 1,712 | |
- | 0.2% | |
2.5 | 9.0 | |
over 1 year ago | 16 days ago | |
C++ | PHP | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rbs_parser
-
Sorbet: Stripe's Type Checker for Ruby
We discovered a bug in `srb init` for Ruby 3.1 recently that a teammate of mine is working on fixing at the moment. It's likely that if you tried again in a few days it'll have been fixed. Sorry about that, totally agree that the out-of-box experience should just work.
I wrote up an FAQ about the state of Ruby 3 and RBS here:
https://sorbet.org/docs/faq#when-ruby-3-gets-types-what-will...
The tl;dr is that RBI files (not RBS files) will probably always be the preferred way to declare types for third party code (because it will always support exactly the same set of features that Sorbet does). We have some people in the community look into teaching Sorbet to read the RBS format, but the existing parsers for RBS files are written in Ruby and are very slow, and there are some ambiguities in the spec that make writing a third party parser that compiles to native code tricky. You can see an attempt to write a fast RBS parser in C++ here[1], but again given that RBI files do everything we need them to right now and we have other features people are asking us for, we haven't prioritized RBS support incredibly highly.
Sorbet works completely fine without RBS files!
[1] https://github.com/Shopify/rbs_parser
-
Open-Sourcing the Sorbet (Ruby) VS Code Extension
This article might help clear some things up:
https://sorbet.org/blog/2020/07/30/ruby-3-rbs-sorbet
tl;dr:
- RBS files are what Ruby 3 uses to describe types in separate files
- RBI files are what Sorbet uses to describe types in separate files
- Sorbet invented its RBI file syntax before RBS files existed. RBI files use the same syntax for types and signatures as in type annotations that live inside `*.rb` source code with Sorbet.
- We've been meaning to add support to Sorbet to consume both RBI files and RBS files, but we haven't had a chance to get around to it.
If someone beat us to it and implemented support for RBS files in Sorbet that would be amazing! Shopify took an early stab at implementing an RBS parser in C++ for performance[1], but I'm not sure what the status of it is today.
[1] https://github.com/Shopify/rbs_parser
-
Sorbet Compiler: An experimental, ahead-of-time compiler for Ruby
(disclaimer: I work on the Sorbet team)
I think I understand GP's motivation: RBI files and RBS files are two different formats, and as a user of the language, people tend to want to use the officially blessed solution the language provides.
In case you weren't aware, parlour[1] is a popular open source project for working with RBI files. I believe it supports transparently converting between RBI files (Sorbet) and RBS files (Ruby 3).
There is also rbs_parser[2], a C++ parser for RBS files to convert them to RBI files, written by Shopify, a major user of Sorbet.
Stepping back: I haven't personally read many complaints from Sorbet users describing how the current state of RBI/RBS interop gets in the way of what they can actually do with Sorbet. Almost all the feature requests we get about Sorbet (both inside Stripe and outside) are for fixing bugs or implementing new language-level features. RBI files as implemented seem to work.
Sorbet already has an extensive set of RBI files covering the Ruby standard library (at least as good or better to my knowledge than any existing repository of types for RBS files), and there are plentiful tools for working with RBI files, listed here.[3]
If lack of first-party RBS support in Sorbet is holding you back from trying Sorbet, I'd strongly encourage you to give Sorbet a try anyways! Many people have shared great experiences adopting Sorbet in their Ruby codebases.
[1] https://github.com/AaronC81/parlour
[2] https://github.com/Shopify/rbs_parser
[3] https://sorbet.org/en/community
Packagist
-
Get YouTube Channel Details API: Testing Connection
What will we do next time? Actually, the whole package is ready, and all that's left is to publish it on Packagist.
-
Building Python Package: API Client for YouTube Channel Details (RapidAPI)
publishing our work on https://packagist.org/
-
Shopware Changes since the 6.0 Dev Training Videos
The latter one is based on nix OS using Symfony flex recipes and PHP packagist composer. The flex devenv should work cross-platform on Linux, Windows, and Mac. "The main difference to other tools like Docker or a VM is that it neither uses containerization nor virtualization techniques. Instead, the services run natively on your machine."
-
Have an interview for PHP, any tips on where to start?
Composer is (still) the defacto standard package manager, with the Packagist repo being the standard place to find and install libraries.
-
Was Rust Worth It?
Sorta—it looks like they were most enforced by convention until May 2015, when they finally become enforced [0]. Still, that's a good one that I hadn't thought of, and they at least had the convention in place.
[0] https://github.com/composer/packagist/issues/163#issuecommen...
-
Best practices for building a production-ready Dockerfile for PHP applications
Scanning your image for vulnerabilities is a critical step before you deploy it to production. You can use Snyk to scan your PHP Docker image and identify and resolve vulnerabilities. The Snyk Vulnerability Database includes records for all popular operating systems and dependencies, including PHP packages published to Packagist.
-
laravel is apple and symfony is android, your own framework is linux distro buit by you
No. The only linked commercial thing I know - is Nova admin panel interface lib. But you don't have to use it. (Filament or Encore are free and suitable). Modules are free ( packagist.org and gthub.com ) and you should handle them with standard composer package tool. But you need to code. It is not WordPress like CMS
-
How to tame a language
Once you understand the underlying principles of a concept, you're free to find a library via packagist.org to use.
-
New to PHP - I'm actually impressed
For strings I use Stringy (https://github.com/danielstjules/Stringy) for arrays I built my own Collection library, but pretty sure there are plenty in packagist (https://packagist.org/)
-
Google Drive API, PHP discontinued.
I guess I tried downloading a old version. and have to download a newer version of apiclient I found on https://packagist.org/packages/google/apiclient with monolog/monolog: ^2.9||^3.0. I'll try that in a second, I am away from computer now.
What are some alternatives?
tapioca - The swiss army knife of RBI generation
Laravel-Zero - A PHP framework for console artisans
sorbet - A fast, powerful type checker designed for Ruby
WordPress Packagist - WordPress Packagist — manage your plugins with Composer
sorbet-typed - A central repository for sharing type definitions for Ruby gems
Laravel 6 - Powerful REPL for the Laravel framework.
crystal - The Crystal Programming Language
Bingo Functional - A simple functional programming library for PHP
solargraph-rails - Solargraph plugin to add awareness of Rails-specific code
Symfony Panther - A browser testing and web crawling library for PHP and Symfony
solargraph - A Ruby language server.
LaravelS - LaravelS is an out-of-the-box adapter between Laravel/Lumen and Swoole.