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

feature/dom merge coalesce order #42

Closed
wants to merge 4 commits into from

Conversation

rkosegi
Copy link
Owner

@rkosegi rkosegi commented Jul 19, 2024

  • Pipeline: trim space from template result before evaluating bool
  • Pipeline: Make default SetOp strategy to merge
  • DOM: Cleanup - inline variable initialization
  • DOM: Reverse order of nodes in coalesce

Signed-off-by: Richard Kosegi <richard.kosegi@gmail.com>
Based on current usage pattern analysis, 'replace' strategy
is used less often then 'merge'.

Signed-off-by: Richard Kosegi <richard.kosegi@gmail.com>
Signed-off-by: Richard Kosegi <richard.kosegi@gmail.com>
Overriden value should be evaluated first, otherwise override will never work.
Move coalesce to appropriate merge*.go files and add unit test for this situation

Signed-off-by: Richard Kosegi <richard.kosegi@gmail.com>
Copy link

sonarcloud bot commented Jul 19, 2024

Copy link

codecov bot commented Jul 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.34%. Comparing base (a5fbc11) to head (cb47454).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #42   +/-   ##
=======================================
  Coverage   99.34%   99.34%           
=======================================
  Files          37       37           
  Lines        1993     1993           
=======================================
  Hits         1980     1980           
  Misses          6        6           
  Partials        7        7           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@rkosegi rkosegi closed this Jul 19, 2024
@rkosegi rkosegi deleted the feature/dom-merge-coalesce-order branch July 19, 2024 07:01
@rkosegi rkosegi restored the feature/dom-merge-coalesce-order branch July 19, 2024 07:02
@rkosegi rkosegi deleted the feature/dom-merge-coalesce-order branch July 19, 2024 07:05
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