-
Notifications
You must be signed in to change notification settings - Fork 24
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
Added alias support for queries and mutations #26
Conversation
* Update Spek version * Fix print wrong escaped character, Fix VerachadW#4 * Rewrite the GraphQLPrintSpek for preetty print test * Bump hotfix version * Update build status link
* bump to kotlin v1.1.1 * Add type alias for more readable code * Change the package name to me.lazmaid.kraph * Fix build failed dur to hamkrest error * Update spek version * Update ENV for release * Update README
* WIP * Split the print logic into sealed class * Update UTs * Add exception message * Refactor
* Add Test Coverage * Update spek version * Fix test result path * Add codecov YAML * Add onlyIf * Update config * Fix travis command * Add coverage badge
* Add support for boolean type * Add Tests
missing "h" in the example call to `println(query.toGrapQueryString())`
* improve readme * Allow using field with a block in place of field object * Update readme to include new changes * Cheap implementation of fragment that doesn't use actual GraphQL Fragments * Add fragment docs to readme * Fix tests * Change function to 'defineFragment'
* Update .gitignore * Update dependecies * Add secondary constructor for DataEntry.NonDecimalNUmber * Add Test for DataEntry classes * Fix failed UTs
* improve readme * Allow using field with a block in place of field object * Update readme to include new changes * Cheap implementation of fragment that doesn't use actual GraphQL Fragments * Add fragment docs to readme * Fix tests * Add separate methods to print the different parts of the request separately * Use spaces instead of newlines for request format * Rewrite printing operations to optionally escape quotes * update readme a bit * Change function to 'defineFragment' * Use an enum to choose print format and write tests to cover all formats * Add note about variables
* add support for variables * add support for variables
Hey @PaulProject. Thanks for the PR. Could you please check the errors from CI Build and add some example for usage as well? |
I have a problem with run JUnit tests. I installed Spek plugin for AS 3.2.1, run tests and see error:
|
Hi, how are you? |
@PaulProject Sorry for the delay. Quite busy here. I will check by today. Could you show me your version of Spek plugin? Did you have the latest version? |
I just changed the target branch to develop. Try to update and rerun again |
…as_support # Conflicts: # build.gradle Replace /n on """ in the BuilderSpek.kt
Codecov Report
@@ Coverage Diff @@
## develop #26 +/- ##
=============================================
- Coverage 83.43% 82.38% -1.05%
- Complexity 69 70 +1
=============================================
Files 16 16
Lines 157 159 +2
Branches 29 30 +1
=============================================
Hits 131 131
- Misses 9 10 +1
- Partials 17 18 +1
Continue to review full report at Codecov.
|
Hello, Verachad. I'm ready to merge. Do you know, GitHub is able squash commits when merge request is accepted? |
@PaulProject Hey, I think we are good to merge. Could you also write HOW-TO in README.md as well? |
Yes of course, give me some time |
# Conflicts: # README.md # core/src/main/kotlin/me/lazmaid/kraph/Kraph.kt # core/src/main/kotlin/me/lazmaid/kraph/lang/DataEntry.kt # core/src/main/kotlin/me/lazmaid/kraph/lang/Field.kt # core/src/main/kotlin/me/lazmaid/kraph/lang/GraphQLNode.kt # core/src/main/kotlin/me/lazmaid/kraph/lang/relay/Node.kt # core/src/main/kotlin/me/lazmaid/kraph/lang/relay/RelayMutation.kt # core/src/test/kotlin/me/lazmaid/kraph/test/BuilderSpek.kt # core/src/test/kotlin/me/lazmaid/kraph/test/DataEntrySpek.kt # core/src/test/kotlin/me/lazmaid/kraph/test/GraphQLPrintSpek.kt # core/src/test/kotlin/me/lazmaid/kraph/test/RequestSpek.kt
I have some conflicts. Do I need to resolve it? |
I resolve the conflicts, do I need to push the change? |
@PaulProject Yes, please |
Hi @VerachadW, what do you think about code coverage? Do I need to fix the checks? |
@PaulProject Yes, please. |
@PaulProject How was the coverage? Could you be able to fix it? It wants to have 1 version release before next year. If possible, I want your changes as well. |
Hi, I don’t have any time for fix it. I have a problem with run the tests (I wrote about it) and I can’t check the code coverage. If you can help me, we do it. |
No description provided.