Skip to content
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

Improve instruction & labelling on "Add Device" dialog #2434

Merged
merged 1 commit into from
Jul 7, 2023

Conversation

joepavitt
Copy link
Contributor

Description

Improve the language & labelling on the "Add Device" modals. Better informing users of functionality available.

Related Issue(s)

Fixed #2428

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on flowforge/helm to update ConfigMap Template
    • Issue/PR raised on flowforge/CloudProject to update values for Staging/Production

Labels

  • Backport needed? -> add the backport label
  • Includes a DB migration? -> add the area:migration label

@joepavitt joepavitt requested a review from Pezmc July 7, 2023 13:01
@Pezmc Pezmc merged commit 183abd5 into main Jul 7, 2023
2 checks passed
@Pezmc Pezmc deleted the 2428-device-type-description branch July 7, 2023 13:17
</FormRow>
<FormRow v-model="input.type" data-form="device-type" :error="errors.type" :disabled="editDisabled" container-class="w-full">
<template #default>Type</template>
<template #description>Use this field to better identify your device, and sort/filter in your device list.</template>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The type field becomes much more useful at the edge:

For example, you might deploy the same flow to 2 physically different device types. The env var FF_DEVICE_TYPE can be used in switch nodes for routing messages, doing different things, accessing alternative edge connected things etc.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

didn't realise that FF_DEVICE_TYPE was an env var made available either. May be worth extending this description with something along those lines if you don't mind?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Not clear what significance of "type" is when adding a device
3 participants