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

Refactor publication type validation #842

Merged
merged 65 commits into from
Jan 18, 2023

Conversation

caendesilva
Copy link
Member

No description provided.

@caendesilva caendesilva force-pushed the refactor-publication-type-validation branch from 63240b5 to 66feecf Compare January 18, 2023 13:53
@codecov
Copy link

codecov bot commented Jan 18, 2023

Codecov Report

Merging #842 (95b1fd4) into publications-feature (858469c) will not change coverage.
The diff coverage is n/a.

@@                   Coverage Diff                    @@
##             publications-feature      #842   +/-   ##
========================================================
  Coverage                  100.00%   100.00%           
- Complexity                   1585      1595   +10     
========================================================
  Files                         172       173    +1     
  Lines                        3954      3960    +6     
========================================================
+ Hits                         3954      3960    +6     
Impacted Files Coverage Δ
...p/packages/publications/src/PublicationService.php 100.00% <0.00%> (ø)
...ckages/publications/src/Models/PublicationType.php 100.00% <0.00%> (ø)
...s/src/Commands/ValidatePublicationTypesCommand.php 100.00% <0.00%> (ø)
...ications/src/Actions/ValidatesPublicationField.php
...cations/src/Actions/PublicationSchemaValidator.php 100.00% <0.00%> (ø)
...ications/src/Actions/PublicationFieldValidator.php 100.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

caendesilva and others added 27 commits January 18, 2023 18:31
These proposed warnings pretty much all only kick in if the user does something that goes against the defaults (and in some cases common sense) and that that point I think it's fair enough if the developer needs to do a tiny bit of debugging. Adding dynamic checks like tagGroup validation and similar add an unjustified amount of complexity at this point in time.
@caendesilva caendesilva marked this pull request as ready for review January 18, 2023 19:12
@caendesilva caendesilva merged commit 99d09f7 into publications-feature Jan 18, 2023
@caendesilva caendesilva deleted the refactor-publication-type-validation branch January 18, 2023 19:12
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