Andrei Kaleshka
Andrei Kaleshka
@dchandekstark I don't think so. The reference you pointed is about evaluating (or data processing) step. But this PR is about types definition and use it with inheritance.
Actually, this PR is not essential. On the project we've come up with the following base class: ```ruby # Example: # # module Map # class UsersLocationsResponseSerializer < ApplicationSerializer #...
It seems that @ernie has no longer supported this gem - the last change was 1 year ago
Added integration with rails 4
I've fixed this project with alias: ```javascript module.exports = withFonts( withOptimizedImages( { webpack: (config) => { config.resolve.alias['@public'] = path.resolve(__dirname, 'public'); return config; }, } ) ); ``` Then you can...
@forest we have such hack in our app either. It would be great to have it merged.
The same issue. It seems to me that SES has changed API and we have this error now...
https://github.com/widefix/actual_db_schema/pull/62
@OuYangJinTing thanks for adding your issue. Can you please specify your real scenario? That would allow me to think of a concrete fix rather than implementing an abstract solution. Thank...
@OuYangJinTing if the original migration had the seeding data populated automatically would it work for you? There is a solution for seeding data within migrations - https://github.com/ka8725/migration_data This is what...