-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gateway antenna location settings (without maps) #716
Conversation
c34eef6
to
f9781dc
Compare
8ccfa20
to
79416c3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only small remarks
@htdvisser do we support only a single gateway antenna?
@connect( | ||
({ gateway, application }, props) => ({ | ||
gateway: gateway.gateway, | ||
application: application.application, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not used
@@ -13,6 +13,7 @@ | |||
// limitations under the License. | |||
|
|||
/* eslint-disable no-invalid-this */ | |||
/* eslint-disable array-callback-return */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this because of how traverse
works?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. It uses a mapping function that does not expect a return value which will cause the linter to nag.
We agreed to have only one antenna location for MVP on slack. |
79416c3
to
70cfb29
Compare
Summary
Closes #713
Dependent on #643 (hence draft PR)Changes
Notes for Reviewers
Complementary implementation to #643.
Release Notes