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

ConfigFileFormat#Properties are now fully compatible with themselves #4033

Conversation

DiegoKrupitza
Copy link
Contributor

@DiegoKrupitza DiegoKrupitza commented Oct 13, 2021

Previously ConfigFileFormat#Properties were not fully compatible by
themself which meant the function ConfigFileFormat.isPropertiesCompatible
was not really meaning full. PropertiesConfigFiles are now designed to be
compatible bythemselves by implementing PropertiesCompatibleConfigFile.
This might be usefull in further development.

Currently DefaultConfigFactory.create will not create a properties
compatible repository since this is not really usefull and a
localRepositry might be easier to use in further development.

What's the purpose of this PR

In PR #4030 we found out that ConfigFileFormat#Properties are not compatible by themselves which might become problematic in the future.

Which issue(s) this PR fixes:

None

Follow this checklist to help us incorporate your contribution quickly and easily:

  • Read the Contributing Guide before making this pull request.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Write necessary unit tests to verify the code.
  • Run mvn clean test to make sure this pull request doesn't break anything.
  • Update the CHANGES log.

Previously `ConfigFileFormat#Properties` were not fully compatible by
themself which meant the function `ConfigFileFormat.isPropertiesCompatible`
was not really meaning full. PropertiesConfigFiles are now designed to be
compatible bythemselves by implementing `PropertiesCompatibleConfigFile`.
This might be usefull in further development.

Currently `DefaultConfigFactory.create` will not create a properties
compatible repository since this is not really usefull and a
localRepositry might be easier to use in further development.
@codecov-commenter
Copy link

codecov-commenter commented Oct 13, 2021

Codecov Report

Merging #4033 (5f8b524) into master (98f7c8b) will increase coverage by 0.01%.
The diff coverage is 77.77%.

Impacted file tree graph

@@             Coverage Diff              @@
##             master    #4033      +/-   ##
============================================
+ Coverage     51.63%   51.65%   +0.01%     
- Complexity     2543     2547       +4     
============================================
  Files           484      484              
  Lines         14839    14844       +5     
  Branches       1536     1536              
============================================
+ Hits           7662     7667       +5     
  Misses         6645     6645              
  Partials        532      532              
Impacted Files Coverage Δ
.../framework/apollo/core/enums/ConfigFileFormat.java 95.23% <0.00%> (ø)
...rip/framework/apollo/spi/DefaultConfigFactory.java 90.00% <85.71%> (-1.67%) ⬇️
...amework/apollo/internals/PropertiesConfigFile.java 71.42% <100.00%> (+6.42%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 98f7c8b...5f8b524. Read the comment docs.

Copy link
Member

@nobodyiam nobodyiam left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution! Here are some minor comments:

@DiegoKrupitza
Copy link
Contributor Author

@nobodyiam everything should be resolved now 👍🏽😌

Copy link
Member

@nobodyiam nobodyiam left a comment

Choose a reason for hiding this comment

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

LGTM

@nobodyiam nobodyiam merged commit 09d2fa3 into apolloconfig:master Oct 17, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Oct 17, 2021
@nobodyiam nobodyiam added this to the 2.0.0 milestone Jan 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants