@asika32764 looks ok any kind of testing required?

BTW: I'm not 100% sure but are you expect namespacing?

throw new \LogicException('Please add a row to content_type');

Also a thing that need to decide e.g. by @infograf768 should we use JText / Language strings here?

I also give this a go, but share the concerns by @zero-24

JText isn't compulsory I think we've decided as long as the front facing user won't see them. The namespacing thing i can solve on merging.

Indeed, any message that will not be displayed to the end user does not 'really' need to be translated in Joomla for 2015.

PHP coders are supposed to practice English or change hobby/profession... at least while English is still the lingua franca ( http://en.wikipedia.org/wiki/Lingua_franca ) used in the World for PHP coding.
Taking into account the much larger increase in population in parts of the World where English is not hegemonic, this could change faster than some think...

See: http://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_speakers

Hello @asika32764

Thank you for your contribution.

The last comment here was on [date]. So the question is, Is this issue/pull request still valid?
If no reply is received within 4 weeks we will close this issue.

Thanks for understanding!

I think this is still valid. this PR is a little improvement to make developer more easier to use UCM, not for end user.

But I'm not sure is there any concerns merging this PR.

@asika32764 UCM is barely used and from what I see, UCM is not going to be further used by the core and will most likely be removed altogether in the future. Given that, I don't think this PR adds much to the core and shouldn't be merged in my opinion. If that is OK with you, I will close the issue.

Thank you for your contributions as always.

Yes, just close it.

Closing as discussed.