Skip to content

Conversation

ishakuta
Copy link
Contributor

@ishakuta ishakuta commented Nov 5, 2015

It's possible to edit enums out of the box from entity management UI, but if it's not allowed for some user, this approach could be helpful:

  • allow to add/edit custom enums, dictionaries and custom entities that have non-integer primary key
  • automatically add menu items for these entities
  • add validation for all enum entities

- allow to add/edit custom enums, dictionaries and custom entities that have non-integer primary key
- add these entities to menu
- add validation for all enum entities
- get modified form data after submit
@orocla
Copy link

orocla commented Dec 22, 2015

Thank you for your pull request.

It looks like this may be your first contribution to an Oro, Inc. open source project, in which case you'll need to sign a Contributor License Agreement (CLA) at http://www.orocrm.com/contributor-license-agreement/

If you've already signed the CLA, it's possible we don't have your GitHub username or you're using a different email address. GitHub uses the email address you set in your local Git configuration to associate commits with your GitHub account. Please sign the CLA again using the correct GitHub username and email address or see this help article on setting the email on your git commits.

Once you've signed the CLA, please allow for about an hour for the submission to be processed.

$groupConfigProvider = $this->configManager->getProvider('grouping');

$withHidden = true; // TODO: move it to configuration
$extendConfigs = $entityExtendProvider->getConfigs(null, $withHidden);
Copy link
Contributor

Choose a reason for hiding this comment

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

you do not need provider here, you can get Configs from configManager instead , e.g.
$this->configManager->getConfigs('extend', null, true)

@alex-n-2k7
Copy link
Contributor

"This branch has conflicts that must be resolved"
Please resolve conflicts

* @return bool
*/
protected function isEnumClass($entityClass)
{
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change to verification by enum code - for enums it should be present in config, e.g. run console command
./app/console oro:entity-config:debug "Extend\Entity\EV_Lead_Source"

in output you'll see something like

    [enum] => Array
        (
            [code] => lead_source
            [public] =>
            [multiple] =>
        )

@alex-n-2k7
Copy link
Contributor

@ishakuta Thanks for your contribution, i think it will be a nice feature.
Also it will be great if you could provide unit/functional tests to cover new functionality ;)

@iklymenko
Copy link
Contributor

@ishakuta hi and tanks for you contribution! Would you be so kind and tell us, are you still interested to finish this PR?

@ishakuta
Copy link
Contributor Author

ishakuta commented Jun 2, 2016

@iklymenko yes I'm interested, I'll try to update it ASAP

@mkudelya
Copy link
Contributor

mkudelya commented Feb 7, 2017

Hi @ishakuta

Enum editing via UI was implemented in system by oro team. This PR is still actual ?

@ishakuta ishakuta closed this Feb 9, 2017
@ishakuta
Copy link
Contributor Author

ishakuta commented Feb 9, 2017

no, it's not, thank you

@ishakuta ishakuta deleted the feature/dict-enum-crud branch February 9, 2017 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

5 participants