Skip to content

Allow dynamic order of elements in webspace xmls #3764

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

alexander-schranz
Copy link
Member

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Fixed tickets fixes sulu/sulu-docs#360
License MIT

What's in this PR?

It allow dynamic order of items in the webspace, template and format xmls.

Why?

For beginners a fix order can be a pitfall.

Example Usage

See sulu/sulu-docs#360 issue.

@alexander-schranz alexander-schranz force-pushed the enhancement/allow-dynamic-order-in-xmls branch from 53d4da4 to 7090426 Compare February 9, 2018 16:50
@alexander-schranz alexander-schranz changed the title WIP: Allow dynamic order in xmls Allow dynamic order of elements in webspace xmls Feb 9, 2018
@alexander-schranz alexander-schranz changed the base branch from master to release/1.5 February 9, 2018 16:51
@danrot danrot requested review from a team, chirimoya, wachterjohannes and trickreich and removed request for a team February 20, 2018 09:41
@danrot
Copy link
Contributor

danrot commented Feb 20, 2018

For me that change is fine, I think it makes writing these XMLs a lot easier, and I don't see any value in demanding a certain order.

But just to be sure, I have requested reviews from the @sulu/core-team, if anybody has any serious concerns about this.

@trickreich
Copy link
Contributor

is totally ok for me..

@danrot danrot merged commit 5959125 into sulu:release/1.5 Feb 20, 2018
@alexander-schranz alexander-schranz deleted the enhancement/allow-dynamic-order-in-xmls branch February 21, 2018 07:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants