You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And then it would be good if this documentation is not using the old Datastax repository as reference but gets updates from yours (as you are the now defacto upstream). And this documentation is then for example used by phpstan and similar tools to validate PHP code.
@JetBrains, any recommendations how this can be achieved?
The text was updated successfully, but these errors were encountered:
This is ScyllaDB first driver, Apache Cassandra Second, I'll be supporting Cassandra as much as possible, that's the thing why no updates were made to PhpStorm (at least I didn't send them). This is in the process of migrating to V2 rewrite in Rust (which I'm doing a bit behind the scenes, testing things around), and a new extension (scylladb.so) with (minor) breaking changes will be created with new stubs which then can be published to PhpStorm.
For the time being, we need to merge the stubs we already have and write more, so that those stubs can be merged on release into single php file. I'll see what can be done.
@DanielHe4rt Can you do something about this, any ideas?
I just drop a ping at @JetBrains Advocate folks to check the possibility to update it. There's a couple of things that we need to understand before update the Cassandra Official Driver documentation, even knowing that they deprecated the full project.
@CharlemagneLasse also, are you using ScyllaDB or Cassandra? Would be cool to know which use-case you're working with on PHP, some queries and so on if it's ok to share.
There were various updates in https://github.com/JetBrains/phpstorm-stubs/commits/master/cassandra/cassandra.php which should be incomporated in your documentation.
And then it would be good if this documentation is not using the old Datastax repository as reference but gets updates from yours (as you are the now defacto upstream). And this documentation is then for example used by phpstan and similar tools to validate PHP code.
@JetBrains, any recommendations how this can be achieved?
The text was updated successfully, but these errors were encountered: