that again (v1) only lists the variables does not indicate if there are any mixins available to use. Guess if there are no docs then the answer is no.

There is nothing in docs about stylus except some info on variables.

Does quasar come with any stylus mixins out of the box?

In particular a breakpoint mixin like this?

http://1pixelout.net/2015/10/02/simple-breakpoint-media-queries-with-stylus/

DRY before diving in.

@s-molinari So did that guide get posted? link please

I love it…a programmer saying “you can ‘simply’”.

Yes I can do that. As I explained it would be a pain to do that. It means I must rebuild that object for each specific page over and over from scratch as it’s used many places through out the site. In a super bad case I’d have to do that twice on the same page. If I could hide/remove in the dom instead then it’s just way way easier. disable already exits why not hide. Guess it’s on me to modify the component to my liking, but could be in the mix for future releases.

@rstoenescu
One wonders what other undocumented props there are, for options in particular. How about hidden:true ? as a companion to disable.

I tired it in the fiddle above and… no go

In my use case it would be a pain to keep recreating the options list for every context (i.e. used on multiple pages) if one member of the list is not applicable to that context.

Better would be to leave the option set members alone and simply set a hidden:true per context.

In the meantime I can use disable. Users will see it but at least they can’t choose it.

@rstoenescu Have you written an upgrade guide (like you did before) that has a specific list of breaking changes from .17?

To disable the text input field without disabling the whole component I ended up doing this to my component.

in the html tag I put

   @keydown="ignore()"
   ref="chip"

then in methods add an ignore method

  ignore () { this.$refs.chip.blur() },

still would be nice to have disable only disable the text field not the whole component.

for those facing this issue just better go check all your icons here. They tell you which one (fab,fas,far) goes with the icon and since the FA upgrade some of your former icon names may be gone
https://fontawesome.com/icons?d=gallery

ok really not clear what needs to be done from you upgrade instructions.

What needs to be done is preface all fa icon classes with fab or fas or far
and not JUST fab necessarily as that stands for branded icons only.
As to which one guess you have try till it works… so not so trivial anymore.

check this FA page out.
https://fontawesome.com/get-started/svg-with-js

https://fontawesome.com/get-started/svg-with-js

to where you sent me not grokking what to change??

No longer use the extras key in config file?
change these somehow?
<q-item-side icon="fa-save" />

how is quasar supposed to know that fa- means fontawesome and how does icon font get loaded now?

    extras: [
      ctx.theme.mat ? 'roboto-font' : null,
      'material-icons',
      'fontawesome'
      // 'ionicons',
      // 'mdi',

    ],