Make PopulateData
lib usage explicit to deal with autoloading issues
#141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Connects to #140.
What does this PR do?
This is is likely a class autoloading problem in staging/production. Even when everything under
/app
is autoloaded in development and eager loaded in staging/production, I'd keep this library out of the app context so we're making thePopulateData::Gobierto
class usage explicit. It is now needed torequire "populate_data"
when making use of that library.How should this be manually tested?
Ensure that the
PopulateData::Gobierto
is properly loaded fromGobiertoAdmin::GobiertoBudgetConsultations::BudgetLineCollectionBuilder
in an eager loaded environment config such asstaging
orproduction
.It is only used in the Consultation Item management action so let's check this form still works:
http:https://gobierto.dev/admin/budgets/consultations/<consultation_id>/items/<consultation_item_id>/edit
.