Currently is you set a component property to an object carrying a BigInt the entire storybook stops functioning. The console logs show an error trying to serialize this object.

Uncaught TypeError: Do not know how to serialize a BigInt
    at JSON.stringify (<anonymous>)
    (...)

Code sample to help you get the context :

const invitations = {
  isLoading: false,
  e

Current behavior

I think there's a mismatch of environment variables being read by babel (JSX config) and Styleguidist, causing some issues deeper down.

(I've noticed this was raised before but was closed)

• build.js sets the env to be production here: https://github.com/styleguidist/react-styleguidist/blob/master/src/s

One of the consumers of our system uses curly braces for content replacement in strings.

Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.

I have tried a number of ways to escape the braces with no luck

Other languages and templating systems seem to use the concept of using double curly b

This code currently does not produce any violations:

class SomeExample(object):
    my_value = 1

    def get_value(self) -> int:
        return self.my_value

    def set_value(self, value: int):
        self.my_value = value

But, it should. We should check if there are two methods with get_ and set_ with the same name and raise a violation.

Related #1054
Rel