robbieaverill

Hey @cameron, the way SilverStripe uses React is really only for the CMS. You're free to use anything you want on your frontend. If you want to use React I'd suggest reading the React tutorials (they're great) and then maybe have a look at how to use GraphQL with React, then go for it. You might also want to pre-render your pages, there are a bunch of tools that will help with that but @unclecheese has written a plugin for Gatsby which might save you some time: https://github.com/silverstripe/silverstripe-gatsby

robbieaverill

you might want to try ... app/tests --filter MyTestClass

👍 (1)
robbieaverill

yeah we updated to php7 a year or so ago but it's probably time to jump to 8 now 😄

👍 (1)
robbieaverill

not all repos have been migrated to xenial yet, so some may still use trusty as the default when you don't specify one

robbieaverill

i think we need to move away from using number_format in the currency logic in silverstripe soon, in order to support proper i18n for currencies. not sure if that get rid of this problem but it sounds like it would. relevant thread: https://github.com/silverstripe/silverstripe-framework/issues/8216

Show 1 attachment(s)
GitHub  
Currency DBField doesn't allow setting different thousands & decimals separators · Issue #8216 · silverstripe/silverstripe-framework

Affected Version 3., 4. Description In some locales, currencies use different separators, eg in Dutch (Netherlands) we use '€1.000,00' (as opposed to '$1,000.00'). The Currency fiel...

Hide attachment content
👍 (1)