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

Mfancher/package updates #696

Closed
wants to merge 70 commits into from
Closed

Mfancher/package updates #696

wants to merge 70 commits into from

Conversation

FancMa01
Copy link
Collaborator

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Vulnerability fix (package bumps or CodeQL adjustments to ensure code security)
  • This change requires a documentation update

Developer Checklist:

  • I have commented my code, particularly in hard-to-understand areas
  • I have resolved any conflicts with the branch I am attempting to merge to.
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings
  • I have ensured that my code does not unecessarily duplicate existing cod
  • I have ensured that all security checks have been passed
  • All input boxes have sensible character limits applied
  • Refreshing related pages puts page in a workable and sensible state

Reviewer Checklist

  • I have pulled the branch into my local environemtn and started the project succesfully
  • I have reviewed the code for proper comments and mispellings
  • All input boxes have sensible character limits applied
  • Refreshing related pages puts page in a workable and sensible state
  • Submitting any relevant Forms relays proper messaging to user
  • I have checked that all security checks have been passed
  • I have checked that all backend routes have proper validation

fanchermatt and others added 30 commits July 20, 2023 08:37
Plugins screen introduced to give users the ability to add Orbit functionality to their installation. Still need to add functionality and security checks to ensure only LNRS users can see and activate
…ications

Add Orbits dashboard page.

Move charts and css into common from notifications to make them shared to be editable and changeable in one spot rather than two.
add charts, need to adjust pulling query to pull everything, not just megaphone
need to adjust teams messages, getting error
Most items should be functional, adding polish and working on notifications.

Still need to finish notifications, "hiding" the plugin for non LNRS users, and only showing screen navigation/allowing screens to be accessed if plugin is active.
add primary and secondary contact
Adjusted orbit integration name to ASR to better encompass the scope of the integration
Change format of integration screen so forms are seperate files, and adjust format of ASR form to include left tabs
@FancMa01 FancMa01 closed this Feb 15, 2024
@FancMa01 FancMa01 reopened this Feb 15, 2024
@FancMa01 FancMa01 closed this Feb 15, 2024
@FancMa01 FancMa01 deleted the mfancher/package-updates branch February 15, 2024 18:39
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