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.

Sign up for GitHub

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

Jump to bottom

Smaller component prefix suggestion #164

Closed
murbanowicz opened this issue Nov 4, 2016 · 5 comments
Closed

Smaller component prefix suggestion #164

murbanowicz opened this issue Nov 4, 2016 · 5 comments
Milestone
v0.9

Comments

@murbanowicz
Copy link
Contributor

Hi,

I think it would be really helpful to not have to write <quasar-*> and get <q-*> instead of that.
@rstoenescu
Copy link
Member

True. Will probably change this so for the first v1.0 beta. Trying to minimize breaking changes as much as possible. Thanks for the suggestion!

@rstoenescu rstoenescu changed the title Change components prefix to make it easier Smaller component prefix Nov 4, 2016
@rstoenescu rstoenescu changed the title Smaller component prefix Smaller component prefix suggestion Nov 4, 2016
@rstoenescu rstoenescu added this to the v1.0 milestone Nov 4, 2016
@rstoenescu
Copy link
Member

Please upvote this thread to make myself an idea on how many of you are interested in this. Thanks!

@dsonet
Copy link

dsonet commented Nov 8, 2016

I suggest simplify the css class prefix as well. It would looks much clean, easy to read and write.

@rstoenescu
Copy link
Member

@dsonet agree on smaller prefix for css classes too

rstoenescu added a commit that referenced this issue Nov 23, 2016
@rstoenescu
perf: #164 Smaller component prefix ("q-" instead of "quasar-")
01b0d93 
This lowers the footprint of Apps too, besides being more faster to type.
@rstoenescu rstoenescu modified the milestones: v0.9, v1.0 Nov 23, 2016
@rstoenescu
Copy link
Member

v0.9 will have the shorter version of prefix.

@rstoenescu rstoenescu mentioned this issue Nov 28, 2016
Closed
@snyk-bot snyk-bot mentioned this issue Jun 2, 2020
Open
@jamijam jamijam mentioned this issue Mar 15, 2021
Open
@snyk-bot snyk-bot mentioned this issue Apr 16, 2021
Open
@Hashen110 Hashen110 mentioned this issue Jan 9, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v0.9
Development

No branches or pull requests
3 participants
@dsonet @rstoenescu @murbanowicz