automatic-api
Here are 35 public repositories matching this topic...
-
Updated
Feb 26, 2022 - Vue
-
Updated
Feb 23, 2022 - Haskell
-
Updated
Feb 26, 2022 - TypeScript
-
Updated
Jan 26, 2022 - Go
Could be useful to add (beside dbAuth.usernameColumn and dbAuth.passwordColumn) the possibility to configure the request fields (like dbAuth.usernameRequestField) to bind a specific request filed to the relative column of the auth table.
If I'm not mistaken the current state imposes username and password as mandatory fields for the request.
What would you like to be added:
It would be amazing to have a "Deploy with Heroku" button. Someone please help and build this.
https://devcenter.heroku.com/articles/heroku-button
Why is this needed:
-
Updated
Feb 21, 2022 - Python
-
Updated
Aug 15, 2021 - Go
-
Updated
Feb 25, 2022 - Shell
-
Updated
Mar 17, 2021 - PLpgSQL
-
Updated
Jun 6, 2021 - JavaScript
-
Updated
Jan 12, 2022 - Java
-
Updated
May 17, 2021 - Kotlin
-
Updated
Sep 2, 2019 - JavaScript
-
Updated
Jan 7, 2022 - PLpgSQL
Problem
We have decided to use attnums
when passing a column reference as arguments but most of the SQLAlchemy operations use column name, so we need to fetch the column name before an SQLAlchemy operation, this can lead to referencing a wrong column in case there are multiple SQLAlchemny operations within a single function and one of those happens to change a column name.
Proposed sol
-
Updated
Oct 16, 2018 - Java
-
Updated
Jul 30, 2021 - Java
-
Updated
May 27, 2020 - Dockerfile
-
Updated
Jun 6, 2020 - Python
-
Updated
Feb 12, 2022 - Go
-
Updated
Feb 17, 2022 - JavaScript
-
Updated
Feb 11, 2020 - Python
-
Updated
Apr 5, 2020 - Java
-
Updated
Nov 22, 2020 - Go
-
Updated
Dec 9, 2021 - Go
-
Updated
Jul 15, 2021 - TypeScript
Improve this page
Add a description, image, and links to the automatic-api topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the automatic-api topic, visit your repo's landing page and select "manage topics."
Issue split from hasura/graphql-engine#6951
our pytest output has a pretty low signal:noise ratio, and it's often difficult to understand the cause of a test failure, if there is one. [Example: a 8600-line log for what turned out to be a flaky test that passed on a second run](https://app.circleci.com/pipelines/github/hasura/graphql-engine-mono/10008/workflows/5e17c7