easy

🚀 Feature Proposal

https://jestjs.io/docs/asynchronous

It currently says "The most common asynchronous pattern is callbacks." This is wrong. We should put promises at the top, and callbacks last. We should probably lift up async-await as well, before the example returning promises.

If you want to work on this, please state so in this issue so not multiple people start working

Description

Given the following component dom:

<div class="group1">
  <muh-component></muh-component>
  <muh-component></muh-component>
</div>
<div class="group2">
  <muh-component></muh-component>
  <muh-component></muh-component>
</div>

There does not seem to exist a concise way to query for component instances within a group of MuhComponent using `spectator.query(M

Feature

When a resource has a lot of fields and the edit form view is very long, it can be easy to forget to scroll back up to the top to hit save. It would be nice if resources had a configuration option that allowed for optionally displaying the save button at the bottom of the form as well.

• **As a bonus, it might

based on: https://kafka.js.org/docs/configuration and tulios/kafkajs#298
We may not have the correct settings for the JSConsumer and JSProducer. This issue is to ensure we have them up to date after nodefluent/node-sinek#154 has been merged