-
Notifications
You must be signed in to change notification settings - Fork 668
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
Enable extensions based on composer.json instead of those loaded at runtime (fixes #5482). #7107
Enable extensions based on composer.json instead of those loaded at runtime (fixes #5482). #7107
Conversation
src/Psalm/Internal/Provider/ReturnTypeProvider/PdoStatementReturnTypeProvider.php
Show resolved
Hide resolved
public const PARAM_LOB = 3; | ||
public const PARAM_STMT = 4; | ||
public const PARAM_BOOL = 5; | ||
// public const PARAM_STR_NATL = 1073741824; since 7.2 |
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'm not sure how to make this only available in 7.2, I'd rather not make a whole new stub file, but it doesn't look like psalm supports @since
? Not immediately necessary anyway.
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.
Yeah, recurrent issue. It should not be an issue if we start generating stubs as we talked
I figure there should probably be an XML config to enable/disable extensions as well, but this seems to work fine so far. |
f5920be
to
46a5e8c
Compare
I was just thinking about |
356192c
to
401b664
Compare
Tests all run fine locally with #7110 merged. I'll see to getting an XML config added and then I think it's good to go. |
Seems like tests are failing. Maybe due to your last commit? |
Odd, they all run fine locally. Must be a PHP version issue. Edit: Wait no, of course, it's because I re-enabled the SOAP extension locally after I got those tests to work the first time. |
I need to read before going and debugging again... |
@orklah anything I can do to streamline review of some of these pull requests? I'm seeing several other pull requests that are going to cause conflicts. |
Ideally I'd like to merge CI fix and CS change before all other PRs. |
@AndrolGenhald Thanks for your PRs, it's really great! I'm having a hard time reviewing everything though! This one is relatively easy to review, but if you could take the habit of summarize your most complex PR to explain the reason behind the biggest changes and challenges you encountered, it would help a lot :) |
Feel free to liberally point out any areas that aren't explained well enough. In the future I'll try to do multiple commits when moving around and deduplicating code sections, I expect being able to see each step in the refactor would help a lot with reviewing. |
Currently rebasing on master, I'll have to open a pull request against 4.x to add |
No, we only documented config properties removal in UPGRADING |
28a3efe
to
63168ac
Compare
@orklah I'm trying to update the baseline on 4.x, but every time I try it's just giving me an empty baseline and saying "No Errors" without actually performing a scan. Any idea what's going on there? It looks like there are also some errors showing up on 4.x that aren't in the baseline, but it's being a bit inconsistent. Might be because I'm trying to modify it manually. |
63168ac
to
5c01913
Compare
@orklah is there any plan to version the documentation on psalm.dev? Maybe add psalm.dev/docs/v4 and psalm.dev/docs/v5 or something? Not sure if I should be removing deprecated stuff from the documentation or not. |
No plan for that no. Changes will be little enough I think and we'll probably advise anyone complaning to update versions anyway... |
Should I add back in the documentation for |
Thanks! |
|
You can add a note in UPGRADING I guess, I'd just like to avoid keeping things in the xml with no uses |
Oh, sorry I wasn't clear enough, I meant the documentation at psalm.dev/docs. If we're not versioning that people will be using Psalm 5 docs for Psalm 4, so we should probably be careful to avoid removing documentation. |
I'm fine with that :) |
Should the need arise we'll provide documentation for previous versions on readthedocs.org, so feel free to remove outdated parts from master. |
No description provided.