hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-18 04:51:35 +03:00
Code Issues Projects Releases Wiki Activity
861 Commits 138 Branches 441 Tags 4.4 GiB
d942266c59
Commit Graph

12 Commits

Author SHA1 Message Date
Shahidh K Muhammed
7ef7e99661
npm audit fix for packages in community folder (#1785) 2019-03-15 12:34:29 +05:30
nizar-m
f83a8e591f rename access-key to admin-secret (close #1347) (#1540) 
Rename the admin secret key header used to access GraphQL engine from X-Hasura-Access-Key to X-Hasura-Admin-Secret.

Server CLI and console all support the older flag but marks it as deprecated.
 2019-02-14 15:07:47 +05:30
Darío Javier Cravero
5739b75000 allow exporting async functions as databases in json2graphql (#1543) 2019-02-01 17:04:36 +05:30
Rishichandra Wawhal
c23fcc8a80 json2graphql update README.md (#1382) 2019-01-15 18:16:11 +05:30
Rishichandra Wawhal
92b071afdf json2graphql: clean up, update readme, add examples (#1375) 2019-01-15 17:10:29 +05:30
Rakesh Emmadi
f6ed169219 allow ordering using columns from object relationships (closes #463) (#672) 
* allow ordering using columns from object relationships, close #463

* validate table fields in nested insert

* add tests

* add docs

* change 'table_order_by' type from enums to ordered map

* remove unwanted code from 'Schema.hs' file

* 'AnnGObject' is not list of field name and value tuple

* update docs for new order_by type

* use 'InsOrdHashMap' for 'AnnGObj'

* handle empty fields in order_by

* remove '_' prefixes for asc/desc

* fix the changed order_by syntax across the repo
 2018-10-26 17:27:33 +05:30
Russ Callahan
fc844bef01 update json2graphql readme (#761) 2018-10-16 17:20:51 +05:30
Rishichandra Wawhal
043b76bab7 sanitise data of special characters before inserting using json2graphql (#770) 2018-10-16 14:53:01 +05:30
Daniel P
b91704e3ca fix typos is multiple files (#728) 2018-10-15 12:29:51 +05:30
Arpit Kushwaha
8454e70614 add some color to hearts (#656) 
fill some colours in those colourless hearts
 2018-10-05 23:46:29 +05:30
Rishichandra Wawhal
3d6732b678 change table and foreign-key naming conventions in json2graphql (#485) 
Foreign keys will now be detected if a column name is `<table_name>_id`.

Earlier, foreign keys would be detected when column name was `<table_name - s>_id`. This was a problem because it placed restrictions on table names. Such restrictions were limiting us from importing complicated JSON databases.

Here are the examples of JSON sampel data for a user, post and comment schema as per new and old conventions:

Old convention:

```
{
    posts: [
        { id: 1, title: "Lorem Ipsum", views: 254, user_id: 123 },
        { id: 2, title: "Sic Dolor amet", views: 65, user_id: 456 },
    ],
    users: [
        { id: 123, name: "John Doe" },
        { id: 456, name: "Jane Doe" }
    ],
    comments: [
        { id: 987, post_id: 1, body: "Consectetur adipiscing elit" },
        { id: 995, post_id: 1, body: "Nam molestie pellentesque dui" }
    ]
}
```

New convention:

```
{
    post: [
        { id: 1, title: "Lorem Ipsum", views: 254, user_id: 123 },
        { id: 2, title: "Sic Dolor amet", views: 65, user_id: 456 },
    ],
    user: [
        { id: 123, name: "John Doe" },
        { id: 456, name: "Jane Doe" }
    ],
    comment: [
        { id: 987, post_id: 1, body: "Consectetur adipiscing elit" },
        { id: 995, post_id: 1, body: "Nam molestie pellentesque dui" }
    ]
};
``` 

@FrediBach I am not sure how this would affect [Blowson](https://github.com/FrediBach/json-data-extender). Can you provide some input?
 2018-09-19 14:18:52 +05:30
Rishichandra Wawhal
68a2e0372f add json2graphql to community tools (#454) 2018-09-17 18:23:23 +05:30