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
Add example archiver and CoreConsole task to generate Archiver into plugin. #6523
Conversation
{ | ||
$this->setName('generate:archiver') | ||
->setDescription('Adds an Archiver to an existing plugin') | ||
->addOption('pluginname', null, InputOption::VALUE_REQUIRED, 'The name of an existing plugin which does not have an API yet'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Text should be "... does not have an Archiver yet"
Off topic: Maybe it makes sense to think about a refactoring of the Archiver in the next 3-4 months. Usually, I build a generator after making the API's simpler to avoid people generating things that will be deprecated later. Providing a very simple API for Archiver would be awesome but also really hard. |
@tsteur - I've included your feedback suggestions. Would you mind taking a look again and letting me know what you think ? Cheers! |
{ | ||
/** | ||
* It is a good practice to store your archive names (reports stored in database) | ||
* in Archiver class constants. You can define as many record namesas you want |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
whitespace missing in nameas
Looks good otherwise, just the two changes and then we can merge. |
@tsteur thanks for feedback. Commited changes to repo. |
Add example archiver and CoreConsole task to generate Archiver into plugin.
Cheers! |
Refs #6516