hurray | Database library

What you are experiencing is called "collapsing margins". Example: If there's an h2 as the first child element inside a div, and the div has no margins, the top margin of the h2 will "go outside the div" at the top - h1, h2 etc. tags have a default margins in practically all browsers (which is a browser setting). To prevent that, you can define all margins for according elements as zero, like I did below with

Add a listener to update the currently selected tab to display the FloatingActionButton, or an empty Container.

While I don't agree that each type of document should get an entire database I will explain how to handle this case.

mongoose handles connections at the db level, While Mongodb allows a single connection to have multiple databases this is not the case here.

This means you'll have to create another mongoose instance and connect to the other database. This also means you can just do require('mongoose') anymore for the none default connection as this would be a different mongoose instance. I recommend creating a singleton that will serve the connection on demand to deal with this.

I will also add that mongoose is VERY inconvenient for this use case, I recommend you reconsider the actual need for another database.

Turns out adding the filter works (s. below). I still don't fully understand how the context population of SpEL VS reactive context works in this scenario, but it works..

It completely depends on how well you want to manage your code which makes refactoring & organising easier.

1. In the above scenario you could keep your states as an exported constant of key value pairs and keep in a central config. Import the constant into which ever components you want to, say component A & B. This way you could easily change the message string without touching any of the components ts & html file when in need.

.find() returns the first item in the array that it finds or undefined.

You have the product object in your variable so you can do it like this.

Okay I got this working,

The whole idea of telling the XSLT compiler about the schema is so that it knows what to expect when it sees the data; the compiler can generate code that makes assumptions about what the data will be like. If the data doesn't conform to the schema, then that negates the whole idea.

It's hard to be specific about exactly what would go wrong if invalid data were accepted, but the XSLT optimiser makes a lot of use of schema knowledge. To take a simple example, if your stylesheet does , and the schema says the element will always have children, then the XSLT processor might well have optimised that to "if true".