-
Notifications
You must be signed in to change notification settings - Fork 222
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
Rename classes, tags and functions #786
Rename classes, tags and functions #786
Conversation
- Add new shorthand methods to GraphQLServices - Change signature of expression functions
- Update documentation accordingly
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.
All these changes make sense but also make the migration from 0.13
to 1.0
a very heavy task. We should maybe introduce all these in a 0.14
version with deprecations so it ease the process.
What do you think of this ?
@mcg-web I think making 0.14 as a transition version is a good idea. |
…refactor/global-variables
56e30ec
to
138b119
Compare
5faf688
to
f8716d7
Compare
@mcg-web I've made it BC, it's ready to be merged. I also removed all UPGRADE files for previous versions. We can have a single UPGRADE.md file in each branch, like |
# Conflicts: # UPGRADE.md # docs/annotations/annotations-reference.md # tests/Config/Parser/AnnotationParserTest.php # tests/Config/Parser/fixtures/annotations/Type/Armored.php # tests/Config/Parser/fixtures/annotations/Type/Character.php # tests/Config/Parser/fixtures/annotations/Type/Planet.php
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.
We should also keep some legacy tests.
* Make all GraphQL services available in the 'expression' constraint * Remove code coverage suppressions * Add GraphQLServices::getAll method
I tweaked some tests to use legacy code, so there are no |
I added some additional checks with reflection to decide, which signature should be used. Here are some examples of which signature is used by certain calls:
|
Implementation of #775
List of renames:
GlobalVariables
->GraphQLServices
ResolverResolver
->QueryResolver
ResolverInterface
->QueryInterface
overblog_graphql.global_variable
->overblog_graphql.service
overblog_graphql.resolver
->overblog_graphql.query
resolver
->query
Also all UPGRADE-files for previous versions have been removed.