doctrine/archived-orm
1
0
Fork 0
mirror of https://github.com/doctrine/orm.git synced 2026-03-23 22:42:18 +01:00
Code Issues 5.3k Packages Projects Releases 100 Wiki Activity

Playground website #6253

New Issue
Closed
opened 2026-01-22 15:29:34 +01:00 by admin · 2 comments
admin commented 2026-01-22 15:29:34 +01:00
Owner
Copy Link

Originally created by @iluuu1994 on GitHub (Jun 18, 2019).

Feature Request

Q A
New Feature yes
RFC yes
BC Break no

Summary

I think it would be greatly beneficial for the Doctrine team and users if there was a playground website where bugs could be reproduced and cross referenced to the issue. I see several benefits:

  1. Incentive to provide simplistic examples, optimally reusable as integration tests
  2. Much easier to create said examples than to create a new project, sample entities, database, etc.
  3. Instantly verifiable by you guys
  4. Instantly verifiable if the bug was fixed by us

Great examples of such websites are:

https://psalm.dev/
https://phpstan.org/

WDYT?

Originally created by @iluuu1994 on GitHub (Jun 18, 2019). ### Feature Request | Q | A |------------ | ------ | New Feature | yes | RFC | yes | BC Break | no #### Summary I think it would be greatly beneficial for the Doctrine team and users if there was a playground website where bugs could be reproduced and cross referenced to the issue. I see several benefits: 1. Incentive to provide simplistic examples, optimally reusable as integration tests 2. Much easier to create said examples than to create a new project, sample entities, database, etc. 3. Instantly verifiable by you guys 4. Instantly verifiable if the bug was fixed by us Great examples of such websites are: https://psalm.dev/ https://phpstan.org/ WDYT?
admin closed this issue 2026-01-22 15:29:34 +01:00
admin commented 2026-01-22 15:29:36 +01:00
Author
Owner
Copy Link

@Ocramius commented on GitHub (Jun 18, 2019):

Feasible with in-memory SQLite, but would need to run in an environment that has no network access. While Psalm/PHPStan do not run code, doctrine does, so the environment needs to be armored.

@Ocramius commented on GitHub (Jun 18, 2019): Feasible with in-memory SQLite, but would need to run in an environment that has no network access. While Psalm/PHPStan do not run code, doctrine does, so the environment needs to be armored.
admin commented 2026-01-22 15:29:36 +01:00
Author
Owner
Copy Link

@iluuu1994 commented on GitHub (Jun 18, 2019):

Feasible with in-memory SQLite

I think that should be sufficient for the majority of issues 👍

While Psalm/PHPStan do not run code, doctrine does, so the environment needs to be armored.

That's true. Maybe the guys from 3v4l.org can help to make it secure.

@iluuu1994 commented on GitHub (Jun 18, 2019): > Feasible with in-memory SQLite I think that should be sufficient for the majority of issues 👍 > While Psalm/PHPStan do not run code, doctrine does, so the environment needs to be armored. That's true. Maybe the guys from [3v4l.org](https://3v4l.org) can help to make it secure.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BC Break
Bug
Can't Fix
Deprecation
Documentation
DQL
Duplicate
Failing Test
Hacktoberfest
Improvement
Improvement
Incomplete
Invalid
Missing Tests
New Feature
PR Created
pull-request
Mirrored from GitHub Pull Request
 Question
Regression
Status: Waiting feedback
Waiting feedback
WIP
Won't Fix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#6253
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?