hannesvdvreken
Repos
98
Followers
216
Following
83

A Guzzle middleware that lets you log HTTP requests in the PHP debugbar timeline.

73
10

Standards either proposed or approved by the Framework Interop Group

12356
2378

Laravel Twillio API Integration

442
151

Laravel is a web application framework with expressive, elegant syntax. We’ve already laid the foundation for your next big idea — freeing you to create without sweating the small things.

71122
22233

Laravel Debugbar (Integrates PHP Debug Bar)

14475
1368

Output complex, flexible, AJAX/RESTful data structures.

3454
335

Events

pull request opened
Laravel v9 support
Created at 6 days ago
pull request opened
Fix docblock

Description of change

Pull-Request Checklist

  • [ ] Code is up-to-date with the master branch
  • [ ] npm run format to apply prettier formatting
  • [ ] npm run test passes with this change
  • [ ] This pull request links relevant issues as Fixes #0000
  • [ ] There are new or updated unit tests validating the change
  • [ ] Documentation has been updated to reflect this change
  • [ ] The new commits follow conventions explained in CONTRIBUTING.md
Created at 2 weeks ago
Created at 2 weeks ago
opened issue
POST / DELETE requests don'
{
  path: '/saml-providers/{slug}',
  method: 'PUT',
  options: {
    auth: 'superadmin',
    pre: [guard('organisation', 'setup_saml')],
    validate: {
      payload: Joi.object({
        crumb: Joi.string().required().min(1), // For some reason this needs to be added manually on PUT.
        domains: [
          Joi.array().items(Joi.string().domain()).required().min(1),
          Joi.string().domain(),
        ],
      }),
      failAction: validationFail,
    },
  },
  handler: save,
}
Created at 1 month ago
opened issue
Transaction is not rolled back on error during migration

Issue Description

Expected Behavior

When running a migration file with transaction "each" option, the transaction should be rolled back on error.

Actual Behavior

When running a migration file with transaction "each" option, the transaction is not rolled back on error.

query: START TRANSACTION
query: ALTER TABLE `users` DROP COLUMN `email`
query: ALTER TABLE `users` DROP COLUMN `non-existent-column`
error: Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version...
Migration "RemoveUserData1643809966646" failed

My Environment

| Dependency | Version | | --- | --- | | Operating System | node-docker | | Node.js version | 16.15.0 | | Typescript version | 4.4.3 | | TypeORM version | 0.3.6 |

Relevant Database Driver(s)

| DB Type | Reproducible | |-------------------| --- | | aurora-mysql | yes | | aurora-postgres | yes | | better-sqlite3 | yes | | cockroachdb | yes | | cordova | yes | | expo | yes | | mongodb | no | | mysql | yes | | nativescript | no | | oracle | yes | | postgres | yes | | react-native | no | | sap | no | | spanner | no | | sqlite | yes | | sqlite-abstract | yes | | sqljs | yes | | sqlserver | yes |

Are you willing to resolve this issue by submitting a Pull Request?

  • ✖️ Yes, I have the time, and I know how to start.
  • ✖️ Yes, I have the time, but I don't know how to start. I would need guidance.
  • ✖️ No, I don’t have the time, but I can support (using donations) development.
  • ✅ No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.
Created at 2 months ago
pull request opened
Set dotenv as sub-dependency

in order not to have to install both:

    "dotenv": "^8.2.0",
    "dotenv-expand": "^8.0.3",
Created at 3 months ago

Set dotenv as sub-dependency

in order not to have to install both:

    "dotenv": "^8.2.0",
    "dotenv-expand": "^8.0.3",
Created at 3 months ago

Update README.md

Created at 3 months ago

updated links

Created at 3 months ago