Skip to content
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

Add Workflow integration #53

Merged

Conversation

alexander-schranz
Copy link
Member

@alexander-schranz alexander-schranz commented Dec 3, 2019

I got the following graphic from @chirimoya and @wachterjohannes about the future publishing workflow in sulu:

Publishing_Workflow

Out of this graphic we have 5 workflow stages / places ....:

  • unpublished: was never published or set to review
  • review: unpublished in review
  • published: page is published
  • draft: page is published but has a draft
  • review_draft: page is published has a draft in review

TODO

  • Add functional ExampleControllerTest

@alexander-schranz alexander-schranz changed the title Add Workflow integration WIP: Add Workflow integration Dec 3, 2019
@alexander-schranz alexander-schranz force-pushed the feature/workflow-behaviour branch 3 times, most recently from 8eff03f to 26a6fc8 Compare December 5, 2019 13:47
@alexander-schranz alexander-schranz force-pushed the feature/workflow-behaviour branch 2 times, most recently from 73c232c to 6c6155e Compare December 9, 2019 09:23
@alexander-schranz alexander-schranz force-pushed the feature/workflow-behaviour branch 10 times, most recently from d05b5fb to 3abc106 Compare December 9, 2019 20:53
@alexander-schranz alexander-schranz changed the title WIP: Add Workflow integration Add Workflow integration Dec 9, 2019
@alexander-schranz alexander-schranz added the Technical Debt Impacts only code quality, no or just small impact on end developers and users label Dec 9, 2019
@alexander-schranz alexander-schranz force-pushed the feature/workflow-behaviour branch 2 times, most recently from 1313dfa to 2b90424 Compare December 10, 2019 10:03
@alexander-schranz alexander-schranz force-pushed the feature/workflow-behaviour branch 3 times, most recently from ff34e18 to 1eb7c9e Compare December 10, 2019 13:56
Content/Application/ContentFacade/ContentFacade.php Outdated Show resolved Hide resolved
Content/Application/ContentFacade/ContentFacade.php Outdated Show resolved Hide resolved
Content/Application/ContentWorkflow/ContentWorkflow.php Outdated Show resolved Hide resolved

private function getWorkflow(): SymfonyWorkflowInterface
{
$definitionBuilder = new DefinitionBuilder();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you move this to a prepend configuration in an additional PR?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

then we could generate the image with symfony commands

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still not sure if its good to prepend the configuration thats why its currently this way.

If the developer want to implements his own workflow on its entity it can be done by set another workflowName on its entity.

Content/Domain/Model/WorkflowInterface.php Show resolved Hide resolved
$contentView = $this->contentLoader->load($content, ['locale' => $locale, 'stage' => 'draft']);
// TODO to support other dimension attributes here
// TODO we should maybe get dimension Attributes form request attributes set by a request listener
// TODO e.g. $request->attributes->get('_sulu_content_dimension_attributes');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@wachterjohannes wachterjohannes merged commit 8ac7361 into sulu:master Dec 11, 2019
@alexander-schranz alexander-schranz deleted the feature/workflow-behaviour branch December 17, 2019 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Technical Debt Impacts only code quality, no or just small impact on end developers and users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants