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

Fixed exporting asset type and status #1816

Merged
merged 1 commit into from Oct 6, 2015

Conversation

mkurek
Copy link
Contributor

@mkurek mkurek commented Oct 5, 2015

In Ralph NG, there is separated asset status for BO and DC (introduced in #1815). This PR fixes export of BO and DC asset statuses to be compatible with NG.

@szok
Copy link
Contributor

szok commented Oct 5, 2015

🆗

@vi4m
Copy link
Contributor

vi4m commented Oct 6, 2015

Your commit message: This PR fix export -> This PR fixes export

In Ralph NG, there is separated asset status for BO and DC (introduced in allegro#1815). This PR fixes export of BO and DC asset statuses to be compatible with NG.
@mkurek
Copy link
Contributor Author

mkurek commented Oct 6, 2015

@vi4m done

@vi4m
Copy link
Contributor

vi4m commented Oct 6, 2015

It should be done with separate package called ralph-interop with DI. Instead, we did just a bastard child of two systems, mixing them, and breaking Classes Encapsulation rules . This horrible practice should be punished, and this pull request should not be merged. But...

Fuck it. New world is coming, let's spend our energy on Ralph-NG instead! :)

@vi4m
Copy link
Contributor

vi4m commented Oct 6, 2015

LLCBDSOTOT
Looks Like Crap But Don't Spend Our Time On It

mkurek added a commit that referenced this pull request Oct 6, 2015
Fixed exporting asset type and status
@mkurek mkurek merged commit 0f0a825 into allegro:develop Oct 6, 2015
@mkurek mkurek removed the review label Oct 6, 2015
@mkurek mkurek deleted the exporter-asset-status-2 branch December 17, 2015 12:54
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.

None yet

3 participants