Skip to content

Solution for avoiding css conflicts especially with name of container. - #80

Merged
vikasrohit merged 1 commit into
devfrom
feature/fix-loader-css-conflict
Apr 14, 2016
Merged

Solution for avoiding css conflicts especially with name of container.#80
vikasrohit merged 1 commit into
devfrom
feature/fix-loader-css-conflict

Conversation

@vikasrohit

Copy link
Copy Markdown

@nlitwin @aselbie @samsep do you see any issue with this renaming of css class name? container is very generic class and is probable for css overriding in the calling app. e.g. in tc-site, this class is causing displacement of loading icon when showing nav bar in tc-site.

@aselbie

aselbie commented Apr 12, 2016

Copy link
Copy Markdown
Contributor

I have no problem with that naming pattern. I think though, that we should move away from webpack extension resolver altogether, since it is incompatible with the default node require system, and therefore doesn't play well with other systems like Mocha.

@vikasrohit

Copy link
Copy Markdown
Author

Thanks @aselbie However, I didn't get the point of extension resolver and its relevance to this change. Can you please elaborate more on this?

@nlitwin

nlitwin commented Apr 13, 2016

Copy link
Copy Markdown
Contributor

I was wondering the same :)

@vikasrohit
vikasrohit merged commit b06194f into dev Apr 14, 2016
@vikasrohit

Copy link
Copy Markdown
Author

Merged for now. Please let me know if you face any problems with after this change.

@vikasrohit
vikasrohit deleted the feature/fix-loader-css-conflict branch October 24, 2017 09:57
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.

3 participants