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

FEDX-1709 Batch/fedx/workiva analysis options v2 #51

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

nicbiggs-wk
Copy link

@nicbiggs-wk nicbiggs-wk commented Nov 6, 2024

Update

This was originally closed here because of failing tests in master, but has been re-implemented with this PR. We are now focusing on implementing v2 for workiva analysis options and commenting out the dart 3 stable and beta CI tests for now. Work to resolve those issues will be handled with FEDX-1911.

What was done

This PR bumps/adds workiva_analysis_options to v2. This is being done in an effort to adopt consistency in {{analysis_options.yaml}} files across the codebase, and ensure all developers are using the most up to date functionality that the dart analyzer can provide.

Failing CI will be evaluated by someone from FEDX and resolved. We will reach out when the pr is ready for review.
(We are stopping dart 3 stable and beta CI tests since they are even failing in master. Future work will resolve this (see Update section above)

If you have any questions, concerns, or opinions, please reach out to #support-frontend-dx.

[Created by Sourcegraph batch change {{Workiva/workiva_analysis_options_v2}}.|https://workiva.sourcegraphcloud.com/organizations/Workiva/batch-changes/workiva_analysis_options_v2]

@nicbiggs-wk nicbiggs-wk marked this pull request as ready for review November 7, 2024 20:20
pubspec.yaml Outdated
@@ -15,6 +15,7 @@ executables:
dependencies:
args: ^2.3.0
build: ^2.1.0
build_runner: ^2.3.3

Choose a reason for hiding this comment

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

Reason for this change? Doesn't look like there is anything within this PR that would warrant promoting build_runner from a dev dep to a regular dep

Copy link
Author

Choose a reason for hiding this comment

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

Good catch, I was trying to fix a CI error and this seemed to resolve it, but I think it was something else that fixed it and this didn't get moved back.

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