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

Coverage fixes #2190

Open
wants to merge 6 commits into
base: feature/embedded-events-editor
Choose a base branch
from

Conversation

thecalcc
Copy link
Contributor

STT-129

Front-end checklist

  • This pull request is adding missing TypeScript types to modified code segments where it's easy to do so with confidence
  • This pull request is using TypeScript interfaces instead of prop-types and updates usages where it's quick to do so
  • This pull request is using memo or PureComponent to define new React components (and updates existing usages in modified code segments)
  • This pull request is replacing lodash.get with optional chaining and nullish coalescing for modified code segments
  • This pull request is not importing anything from client-core directly (use superdeskApi)
  • This pull request is importing UI components from superdesk-ui-framework and superdeskApi when possible instead of using ones defined in this repository.
  • This pull request is not using planningApi where it is possible to use superdeskApi
  • This pull request is not adding redux based modals
  • In this pull request, properties of redux state are not being passed as props to components; instead, we connect it to the component that needs them. Except components where using a react key is required - do not connect those due to performance reasons.
  • This pull request is not adding redux actions that do not modify state (e.g. only calling angular services; those should be moved to planningApi)

@thecalcc thecalcc requested a review from tomaskikutis January 24, 2025 14:00
@thecalcc
Copy link
Contributor Author

  • Improve coverage adding from advanced mode CoverageAddAdvancedModal.tsx - bad condition for disabling "Save" button. If form isn't dirty or coverages have no "assigned_to", Save isn't active. But if you click the checkbox at the left bottom isDirty is set to true -> allowing users to save coverages with no assigned_to. Decide whether do add bad value error messages, or just remove isDirty check.

@thecalcc thecalcc marked this pull request as draft January 27, 2025 09:13
@thecalcc thecalcc marked this pull request as ready for review January 27, 2025 11:02
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.

1 participant