Skip to content

Conversation

@DannyvdSluijs
Copy link
Contributor

This PR adds:

  • A test to proof @param ?string is supported.

This would resolve #13

@DannyvdSluijs DannyvdSluijs changed the title Proof @param ?string is supported in current setup test: Proof @param ?string is supported in current setup Jan 11, 2021
@codecov
Copy link

codecov bot commented Jan 11, 2021

Codecov Report

Merging #50 (80b949f) into master (b5f37db) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #50   +/-   ##
=========================================
  Coverage     89.07%   89.07%           
  Complexity       58       58           
=========================================
  Files             8        8           
  Lines           119      119           
=========================================
  Hits            106      106           
  Misses           13       13           
Impacted Files Coverage Δ
lib/Dispatcher.php 88.88% <100.00%> (ø)

@DannyvdSluijs DannyvdSluijs force-pushed the support-nullable-types-from-docblock branch from e7d79b4 to 35d8013 Compare June 13, 2021 20:25
@DannyvdSluijs DannyvdSluijs force-pushed the support-nullable-types-from-docblock branch from 35d8013 to 80b949f Compare May 19, 2023 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support nullable types (@param ?string $rpcParamName)

1 participant