These are chat archives for symfony2admingenerator/GeneratorBundle
Hi! I would be glad about discussing 2 little questions for issue #82 :
(1) At first I am not sure about to store the information for a group and the credential expression belonging to the group (for each: add/edit/list/show). I would suggest to create a yaml config file during bundle generation process to store the information for every admin config.
(2) In the next step I would use a data provider service to load the groups from the corresponding config , evaluate them and return the allowed groups. So I would be able to exclude the data from controller and start a centralized service. Do I am right by implementing it this way?
groups_servicewhich would require a fully qualified class name, eg
GroupsProvider(which we would create in admingenerator repository)
BaseGroupsProviderwith some helper methods to speed up creating new providers
class MyGroupsProvider implements GroupsProviderwhich holds the logic you proposed in #86 and then simply in all your
generator.ymlyou could link to the same class
s2a_daterange_pickerto FormExtensionsBundle... testing now :)
s2a_daterange_pickeris working, i just need to tweak the default options