Skip to content

Conversation

@TurtIeSocks
Copy link
Collaborator

@TurtIeSocks TurtIeSocks commented Oct 8, 2022

  • Move scan dialog into its own component
  • Move constants out of ScanNextTarget fn
  • Wrap a lot of state changes in useEffects to control renders
  • Consolidate ScanNext and ScanZone components since they were almost identical, with a mode flag to set them apart
  • Generalize some variable names, front and back
  • Use styled components instead of theme overrides
  • Remove unnecessary Slider props and use React Children instead of passing a block prop
  • Disable other map markers when ScanZone popup is open, something is not right when any other markers are activated that can cause the server to get hammered.

Maybe resolves #555

- Move scan dialog into its own component
- Move constants out of ScanNextTarget fn
- Wrap a lot of state changes in useEffects to control renders
- Consolidate repeat functions
- Consolidate repeat dialog
- Consolidate ScanNext and ScanZone components into one reusable component
- Cleanup backend code to use more general variables
-
@TurtIeSocks TurtIeSocks marked this pull request as ready for review October 8, 2022 03:16
@TurtIeSocks TurtIeSocks changed the title ScanNext fixes ScanNext & ScanZone fixes Oct 8, 2022
- Use styled components instead of theme overrides
- Remove unnecessary Slider props and use React Children instead of passing a block prop
- Disable other map markers when ScanZone popup is open, something is not right when any other markers are activated that can cause the server to get hammered.
@TurtIeSocks TurtIeSocks merged commit a09691d into develop Oct 8, 2022
@TurtIeSocks TurtIeSocks deleted the scanNext-react-code-fixes branch October 8, 2022 23:13
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.

2 participants