Skip to content

Conversation

evless
Copy link
Contributor

@evless evless commented Sep 23, 2019

Hi! I added a flag to parser can return default value not only as string type. I don't know, maybe flag is overhead and I can do this case is a default?

@evless evless force-pushed the feat/no-string-default-props branch 2 times, most recently from a2e59ed to c3b84df Compare September 23, 2019 11:36
@pvasek
Copy link
Collaborator

pvasek commented Sep 23, 2019

Would all other test pass if this flag is enabled? Maybe it should really by the default behaviour. The current state seems like bug to me. What do you think?

@evless
Copy link
Contributor Author

evless commented Sep 24, 2019

I think that the current state looks strange, but I don't know all exceptions, maybe it was made on purpose. If this flag is enabled, so 7 tests will fail. I think tests made under string type and I can fix them.

http://s.csssr.ru/U7RQKLD4J/2019-09-24-18-55-09-y9zhv.jpg
http://s.csssr.ru/U7RQKLD4J/2019-09-24-18-55-26-vawcn.jpg

@pvasek
Copy link
Collaborator

pvasek commented Sep 24, 2019

Could you make your changes as a fix? I mean: remove that flag and fix these tests. So your behaviour will be the default one.

@evless evless force-pushed the feat/no-string-default-props branch from c3b84df to 9628c05 Compare September 25, 2019 07:06
@evless
Copy link
Contributor Author

evless commented Sep 25, 2019

I fixed tests and I did my behaviour is default one :)

@pvasek pvasek merged commit 4886f77 into styleguidist:master Sep 25, 2019
@pvasek
Copy link
Collaborator

pvasek commented Sep 25, 2019

Thanks! Published as v1.15.0 on npm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants