lucent/lucent-laravel
2
0
Fork 0
Code Issues 14 Pull Requests Releases 1 Activity

Have a schema generate more than one collection #18

New Issue
Open
opened 2024-10-09 13:39:50 +00:00 by lexx · 1 comment
lexx commented 2024-10-09 13:39:50 +00:00
Owner
Copy Link
Copy Source

This will allow those collections to be "connected" and able to exchange documents via clone or move actions. Would be very useful as a tool for previewing data etc

This will allow those collections to be "connected" and able to exchange documents via clone or move actions. Would be very useful as a tool for previewing data etc
lexx added the enhancement label 2024-10-09 13:39:50 +00:00
lexx commented 2024-10-10 16:56:54 +00:00
Author
Owner
Copy Link
Copy Source

Even better have a schema have a property mirror

Even better have a schema have a property **mirror**
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label enhancement
Milestone
No items
No Milestone
Assignees
Clear assignees
arvanitakis elvira lexx (Alex Lingris) skripkinkostas
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lucent/lucent-laravel#18
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?