Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
base system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Jun 2013 at 06:34 UTC
Updated:
29 Jul 2014 at 22:32 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
ParisLiakos commentedIt can live in devel module, if somewhere
Comment #2
dawehnerdrupal_var_export() was more useful when we exported config in php files, but ctools had it's own version anyway.
Comment #3
catchHold on, iirc this was added explicitly for the db upgrade test scripts. Those need to be human readable for debugging/alterations directly. Needs more review.
Comment #4
ParisLiakos commentedhmm...those scripts are not even working
if i run them from Drupal root as script docs say
If i run them inside the core directory..am i missing something or we should open a critical?
Comment #5
dawehner@ParisLiakos
You should run this script from drupal 7, not drupal 8.
Comment #6
ParisLiakos commentedBoth readable, just with drupal_var_export
array(is not in new line..i guess we can let this file be, if we want our dumps to obey our coding standards
Comment #7
tim.plunkettAgreed we don't need to delete it, but we should still move it.
Comment #8
tim.plunkettComment #9
ParisLiakos commentedi was thinking that maybe Drupal\Core would be more suitable, but other projects could use the same coding standards as Drupal, so why dont make sharing easier?:)
Comment #10
tstoecklerI think drupal_var_export() should at least be marked @deprecated, though.
Comment #11
tim.plunkettYou could have just done that instead of marking NW
Comment #12
catchCommitted/pushed to 8.x, thanks!
Comment #13.0
(not verified) commentedUpdated issue summary