graphql-w-persistent 0.1.0.2 → 0.1.0.3

raw patch · 4 files changed

+22/−9 lines, 4 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

ChangeLog.md +13/−1
graphql-w-persistent.cabal +2/−2
src/Components/DataProcessors/PersistentDataProcessor.hs +1/−0
src/GraphQL.hs +6/−6

ChangeLog.md view

@@ -1,5 +1,17 @@ # Revision history for graphql-w-yesod
 
-## 0.1.0.0 -- YYYY-mm-dd
+## 0.1.0.0 -- 2018-10-18
 
 * First version. Released on an unsuspecting world.
+
+## 0.1.0.1 -- 2018-10-18
+
+* Added documentation
+
+## 0.1.0.2 -- 2018-10-18
+
+* Bug fixes
+
+## 0.1.0.3 -- 2018-10-18
+
+* Update documentation

graphql-w-persistent.cabal view

@@ -10,13 +10,13 @@ -- PVP summary:      +-+------- breaking API changes
 --                   | | +----- non-breaking API additions
 --                   | | | +--- code changes with no API change
-version:             0.1.0.2
+version:             0.1.0.3
 
 -- A short (one-line) description of the package.
 synopsis:            Haskell GraphQL query parser-interpreter-data processor.
 
 -- A longer description of the package.
-description:      This is a general purpose Haskell GraphQL query parser and interpreter. It is including data processing to return GraphQL object formats. The query parser and interpreter are universal (on available query types). It is accepting any string query, and it is returning a list of string database-queries. The data processing unit is designed around the return values from the Yesod and Persistent interface (cast as Text data values from PersistValue). With another server that is same data representation on the returned values from the database, this entire package is applicable. To read more detailed information, you should go to the below module page.
+description:      This is a general purpose Haskell GraphQL query parser and interpreter. It is including data processing to return GraphQL object formats. The query parser and interpreter are universal (on available database query types). It is accepting any string query, and it is returning a list of string database-queries. The data processing unit is designed around the return values from the Yesod and Persistent interface (cast as Text data values from PersistValue). With another server that is same data representation on the returned values from the database, this entire package is applicable. To read more detailed information, you should go to the below module page.
 
 -- URL for the project homepage or repository.
 homepage:            https://github.com/jasonsychau/graphql-w-persistent

src/Components/DataProcessors/PersistentDataProcessor.hs view

@@ -25,6 +25,7 @@ processSubFields sfs rlts = ((showJSON $ toJSObject $ composeGraphQlRow sfs $ fetchGraphQlRow rlts):(processSubFields sfs $ removeDataRow rlts))
 composeGraphQlRow :: [Field] -> [[Text]] -> [(String,JSValue)]
 composeGraphQlRow [] [[]] = []  -- done
+composeGraphQlRow [] ([]:t) = []  -- done
 composeGraphQlRow [] _ = E.throw EOFDataProcessingException
 composeGraphQlRow _ [[]] = E.throw EOFDataProcessingException
 composeGraphQlRow (a:b) ((h:t):j)

src/GraphQL.hs view

@@ -19,18 +19,18 @@ (2) make a list of all above mentioned server objects in separate tuples with a list to all valid scalar subfields as you read them from your database
 (3) make a list of all above mentioned server objects in separate tuples with a list to all valid nested object subfields as you want them to be named and as they are repeated in the later list
 (4) make a list of all above mentioned server objects in separate tuples with a list to all reference database table name(s) as you read them
-(5) make a list of all database table names in separate tuples with a String (of refence to third list relationship names) and a list to the SQL tables that are between the two desired tables; the list order is: 
-identity table name (the first String in this tuple), identity leaving field name, referring table name (the table that's corresponding to the second String in this tuple), referring table entering field name, and (if present) 
-three String sequences that is itermediate table name, intermediate table entering column name, and intermediate table leaving column name. The intermediary table are order from closest to indentity table to closest to referencing table.
+(5) make a list of all database table names in separate tuples with another String (with reference to third-mentioned list on relationship-names) and a list to the SQL database tables that are between the two first tables; the list order is...
+identity table name (the first String in this tuple), identity leaving-field name, referring table name (the table that's corresponding to the second String in this tuple), referring table entering-field name, and (if present) 
+three String sequences that is itermediary-table name, intermediary-table entering-column name, and intermediate-table leaving-column name. The intermediary tables are ordered from closest to indentity table to closest to referencing table.
 
-These lists are later used for arguments in a query parsing function.
+These lists are later used as arguments in a query parsing function.
 -}
 module GraphQL (
     -- * Functions
-    -- *** This is the available methods which are giving access to the package interpretation, validation, and formatting features.
+    -- *** These are available methods to give access to the package interpretation, validation, and formatting features.
     module GraphQL,
     -- * Server data types
-    -- *** These are server data types that are return from processQueryString. You do not need to know these to know how is this package used, but you'll get some insight to what is used to store and map your GraphQL data.
+    -- *** These are server data types that are return from processQueryString. You do not need to know these to know how is this package used, but you'll get some insight to what is used to store and organize your GraphQL data.
     module Model.ServerObjectTypes
     ) where