You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A table using a default value for a decimal column results in an error when building mock files. I tested this by creating a new rails app with the following schema:
On active_mocker v 2.2.3, running rake_active_mocker:buildwith verbosity 3 results in the following: (full stack trace omitted)
TestDatum has the following errors:
unexpected token kEND
warn
unexpected token kEND
/Users/john/.rvm/gems/ruby-2.1.7/gems/parser-2.3.1.2/lib/parser/diagnostic/engine.rb:71:in `process'Parser::SyntaxErrorError Summaryerrors: 0, warn: 1, info: 0Failed models: TestDatum1 mock(s) out of 1 failed.
Downgrading to version 2.0.0 results in a successfully generated mock class. However, the #attributes method is partially commented out due to #<BigDecimal> being inserted as a value for decimal attributes, resulting in a syntax error.
@jdcalvin Let me know if you have other issues and I try to address them ASAP. Also if you have any reasonable feature requests they'll be high priority.
A table using a default value for a decimal column results in an error when building mock files. I tested this by creating a new rails app with the following schema:
On active_mocker v 2.2.3, running
rake_active_mocker:build
with verbosity 3 results in the following: (full stack trace omitted)Downgrading to version 2.0.0 results in a successfully generated mock class. However, the #attributes method is partially commented out due to
#<BigDecimal>
being inserted as a value for decimal attributes, resulting in a syntax error.I'm trying to upgrade from 1.8.3, and the mock file generated will correctly show the value in this version:
The text was updated successfully, but these errors were encountered: