-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x-follow-button #59
x-follow-button #59
Conversation
92801c8
to
791020a
Compare
e15a8ad
to
a939270
Compare
@kateloschinina i just merged master into this branch, and we've added ESLint which has a few errors on this branch, can you fix them please?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry for the delay!
components/x-follow-button/src/styles/mixins/lozenge/_themes.scss
Outdated
Show resolved
Hide resolved
components/x-follow-button/src/styles/mixins/lozenge/_themes.scss
Outdated
Show resolved
Hide resolved
...as they cause issues when other components import these styles using CSS modules :global
Post the update whilst rebasing to master
091b32f
to
eb9e0ac
Compare
- Use regular story configuration - Clean code from the old-styled stories
1634b3c
to
4b5843b
Compare
Note: the build is currently failing as #415 is to be merged in first. |
So that we can use Sass in components. This also adds all the bower paths to the sass load path. Which works for the moment but might need making more robust in the future.
So that we can include it in projects that use other components that use the latest changes.
@kateloschinina I've gone ahead and pulled the changes from #415 into here but made webpack find the bower_component folders itself rather than using symlink which it can do at run time. |
{ | ||
loader: require.resolve('sass-loader'), | ||
options: { | ||
includePaths: glob.sync('./components/*/bower_components', { absolute: true }), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice solution
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a bit of a hack because if two different components depend on different versions of bower things then it could get sticky. but it gets this moving and we can iterate that later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#183 should fix that in the future
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i reckon this is good to go. it's used in production already so
Thank you so much! 🌟 (can't believe it's merged - first commit of this PR made by me on 24 May 2018 😆) |
🎉 🎉 🎉 |
Using concept name as button text:
Using generic button text:
Currently in use directly by
next-myft-page
andft-app
, and as a dependency ofx-topic-search
.