Jonas Cosandey

If i understand the word pristine correctly, we should probably change the docs rather than the result since a changeset is pristine if the changeset is equal to the state...

on a side note; is it possible to dynamically set the `as` attribute since i use my component for multiple models and they have different QP names.

I actually found somewhat of a solution for my problem: ```js const QueryParams = new QueryParams( { inFilter: { defaultValue: null, refresh: true }, notInFilter: { defaultValue: null, refresh: true...

I haven't tested this fully with tracking context yet but its a work in progress and i figured i'd open a draft pr.

I know it's not necessarily nice to put values on a function object, but i think the ergonomics of this approach are quite nice. I also played around a bit...

> > had some problems with context and reassigning the values. > > I think we'll still want to explore putting things on the `State` class -- what problems were...

I see, that`s a very good argument :smile: . I'm not really a typescript user and am more used to a more "functional" programming style so that's why i tried...

@NullVoxPopuli I implemented the function on the class as you proposed an the test is now green, feel free to have a look at this again :smile:

@wycats Would it be an option to add a flag (like we have with the prototype extension) for this so we don't have to break the existing api but can...

@topisani Hey, i just stumbled upon this via #2536 while searching for a way to replace JS `=>` arrow functions with `→`. Is there some new progress on this? This...