Just some quick thoughts:

{}

• Less ways to check if empty and dont have to check for null and undefined
• Our iron-query-params will always serve a {}
• More-strict and easier to make future updates upon (it's harder to take away "features" over time)

null

• fails fast
• user has more freedom for changes
• user will know whether query params has been initialized (e.g. null vs object)

from app-route.

That's a good shortlist of pros for each.

From a bike shed-y perspective, I like {}. Consider the following condition: el.set('route.queryParams.foo', 1). If 'route.queryParams' is an empty object, this will set foo to 1, and the (previously absent) query string in my browser location bar will reflect the change. However, if 'route.queryParams' is null, Polymer's data-binding system will silently disregard the change.

from app-route.

I personally lean {} for completely arbitrary reasons and the ones listed above.

from app-route.

Does this need more discussion? Have we landed on {}?

from app-route.

I think we did land on {} source

from app-route.

I'm gonna close this, since it seems resolved. We can re-open if it isn't 🐙

from app-route.