Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[WiP] Document Workflow 4.3 changes #11211

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

Closed
wants to merge 4 commits into from

Conversation

pbowyer
Copy link
Contributor

@pbowyer pbowyer commented Mar 23, 2019

Document the changes in https://github.com/symfony/workflow/blob/master/CHANGELOG.md and https://github.com/symfony/symfony/blob/master/UPGRADE-4.3.md#workflow:

WiP, more to be added. Community input/commits very welcome!

@@ -80,7 +81,8 @@ like this:
<framework:workflow name="blog_publishing" type="workflow">
<framework:audit-trail enabled="true"/>

<framework:marking-store type="single_state">
<framework:marking-store type="method">
<framework:argument>false</framework:argument>
<framework:argument>currentPlace</framework:argument>
</framework:marking-store>

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't use XML config, can someone please provide the initial_places code for it.

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

It would be nice to add it in the code doc.
Here is the final ref

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I believe I've done this correctly!

@noniagriconomie
Copy link
Contributor

Hi
Just wanted to notify you this PR #10751 (to be merged soon i think)

Copy link
Member

@lyrixx lyrixx left a comment

Choose a reason for hiding this comment

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

Thanks a lot for this PR.


This is an extract of the upcomming blog post:
I hope it will help you to update this PR.


A subject in a state machine can be in only one state whereas a subject in a
workflow can be in one or more places. From the first day of the Workflow
Component we let the user to be able to use a Workflow with a Single State
Marking Store. This was a mistake and this added some useless complexity.

As of now, If your subject can be in only on state: use a state machine. In that
case, the property (marking by default) will be a string. If the subject can
be in many places: use a workflow. In that case, the property will be an array.

@@ -80,7 +81,8 @@ like this:
<framework:workflow name="blog_publishing" type="workflow">
<framework:audit-trail enabled="true"/>

<framework:marking-store type="single_state">
<framework:marking-store type="method">
<framework:argument>false</framework:argument>
<framework:argument>currentPlace</framework:argument>
</framework:marking-store>

Copy link
Member

Choose a reason for hiding this comment

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

It would be nice to add it in the code doc.
Here is the final ref

@pbowyer
Copy link
Contributor Author

pbowyer commented Apr 7, 2019

Thanks for the review @lyrixx! I'll wait for #10751 to merge, rebase and then incorporate your feedback 👍

@xabbuh
Copy link
Member

xabbuh commented Apr 7, 2019

@pbowyer #10751 is merged, sorry for the delay.

@pbowyer pbowyer force-pushed the feature/workflow-4.3 branch from d8a19c3 to 6c636cb Compare April 7, 2019 12:37
@javiereguiluz
Copy link
Member

@pbowyer I regret to inform you that we've just merged a full reorganization of Workflow docs. This will introduce conflicts with your PR. I was postponing the merge, but it was only making things worse. If you don't want to rebase and fix the conflicts, I can create a new PR for you with your changes. I'm sorry.

The main changes are:

  • /workflow.rst now contains the full usage example (everything tht previously was in /workflow/usage.rst
  • The old /workflow.rst contents and the /workflow/state-machines.rst contents have been moved to a new introduction article: /workflow/introduction.rst
  • /workflow/usage.rst and /workflow/state-machines.rst have been deleted.

@@ -224,90 +227,11 @@ you can get the workflow by injecting the Workflow registry service::
// ... if the transition is not allowed
}

// Update the currentState on the post passing some contextual data
Copy link
Contributor

Choose a reason for hiding this comment

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

why do you remove this one?

@xabbuh xabbuh changed the base branch from master to 4.3 May 9, 2019 07:47
@noniagriconomie
Copy link
Contributor

@pbowyer is this PR still relevant now ?
Can you check with latest 4.3 doc? Thx

@pbowyer
Copy link
Contributor Author

pbowyer commented May 25, 2019

is this PR still relevant now ?

I don't know. There appears to be no coordination and people duplicating work in this repository, so I'm not committing any more time until that's clear.

If you want to adopt this PR, fork it - you have my blessing.

@noniagriconomie
Copy link
Contributor

Ok

@noniagriconomie
Copy link
Contributor

@javiereguiluz i think we can close
I may reopen a pr with a part of it, event if i think now we have doc that is relevant

@OskarStark
Copy link
Contributor

Because of the blessing of @pbowyer, I close this PR. @noniagriconomie please add the missing parts in a new PR.

Anyway thanks for your work 👍🏻👍🏻

@OskarStark OskarStark closed this May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants