Skip to content
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

New Feature for custom style injection #69

Merged
merged 9 commits into from
Jun 16, 2018

Conversation

rcostalenz
Copy link
Contributor

Please check if the PR fulfills these requirements

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Introduces a new feature to inject CSS classes into the component.

What is the current behavior? (You can also link to an open issue here)

The dev has to use the current class names to change the style.

What is the new behavior (if this is a feature change)?

Dev can use existing classes.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No new changes are necessary to current users.

Other information:

Roberson Costa added 4 commits June 16, 2018 19:31
Added new prop "styles" which allow the developer to inject classes names to the following selectors:
vueSimpleSuggest
inputWrapper
defaultInput
suggestions
suggestItem
This with the "destyled" prop allow the user to use css frameworks like Bootstrap more easily.
Added new prop "styles" which allow the developer to inject classes names to the following selectors:
vueSimpleSuggest
inputWrapper
defaultInput
suggestions
suggestItem
This with the "destyled" prop allow the user to use css frameworks like Bootstrap more easily.
Copy link
Contributor

@kaskar2008 kaskar2008 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rcostalenz, this is a great feature, actualy. Thank you for your contribution :)
Just a minute ago I wanted to add a remark to suggestItem class, but you've already fixed it :D

@Raiondesu any comments?

@Raiondesu
Copy link
Contributor

I agree with @kaskar2008, the feature is great overall.
@rcostalenz, I think you forgot to add customizable classes for misc-item-above and misc-item-below, though. :)
I think we'll accept your PR once you fix this little detail. :)

@Raiondesu Raiondesu added good first issue Good for newcomers next release This is a thing to include in the next release minor This is a thing to include in the next minor release labels Jun 16, 2018
@rcostalenz
Copy link
Contributor Author

Fix it! I am glad you guys like it.

@kaskar2008
Copy link
Contributor

@rcostalenz, @Raiondesu I think it can't be done that way because slot is not a real dom element and it's not rendering itself as an element, so class bindings on slot is not a workaround. Any ideas how we can pass classes through?

@kaskar2008
Copy link
Contributor

And I think those misc items can also be not a single element tho.

@Raiondesu
Copy link
Contributor

@kaskar2008 Hmm

@Raiondesu
Copy link
Contributor

@kaskar2008 This got me thinking now

@rcostalenz
Copy link
Contributor Author

Actually, since slot can be fully customizable with templates there is no reason to have those, I remove them

@kaskar2008
Copy link
Contributor

@rcostalenz Ok then

@kaskar2008 kaskar2008 merged commit 02dc1f5 into KazanExpress:master Jun 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers minor This is a thing to include in the next minor release next release This is a thing to include in the next release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants