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

Add a config value for the DAG cutoff #143

Merged
merged 5 commits into from
Dec 19, 2017
Merged

Conversation

tiffon
Copy link
Member

@tiffon tiffon commented Dec 19, 2017

Fixes #130 by adding dependencies.dagMaxNumServices UI config property.

Also adds deprecations for config properties.

TLDR; I moved a config property but it's backwards compatible.

Seemed to make sense to group dependencies UI config values in a dependencies top-level property rather than having two top-level properties for it. So, I added deprecations which is an Array of old/new config property names. The getConfig() function moves old settings to the new property name unless there is a conflict. The first time this happens there is a warning issued to the console.

Signed-off-by: Joe Farro <joef@uber.com>
Signed-off-by: Joe Farro <joef@uber.com>
@codecov
Copy link

codecov bot commented Dec 19, 2017

Codecov Report

Merging #143 into master will increase coverage by 0.31%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #143      +/-   ##
==========================================
+ Coverage   92.72%   93.04%   +0.31%     
==========================================
  Files          82       85       +3     
  Lines        1829     1854      +25     
  Branches      353      359       +6     
==========================================
+ Hits         1696     1725      +29     
+ Misses        122      119       -3     
+ Partials       11       10       -1
Impacted Files Coverage Δ
src/components/TracePage/TracePageHeader.js 92.85% <ø> (ø) ⬆️
...ponents/SearchTracePage/TraceResultsScatterPlot.js 36.36% <ø> (ø) ⬆️
...rc/components/SearchTracePage/TraceSearchResult.js 100% <ø> (ø) ⬆️
src/constants/default-config.js 100% <100%> (ø)
src/utils/config/get-config.js 100% <100%> (+22.22%) ⬆️
src/constants/index.js 100% <100%> (ø)
src/utils/config/process-deprecation.js 100% <100%> (ø)
src/components/DependencyGraph/index.js 100% <100%> (ø) ⬆️
src/components/App/TopNav.js 94.11% <100%> (ø) ⬆️
... and 3 more

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 7c8f3d8...749296d. Read the comment docs.

// See the License for the specific language governing permissions and
// limitations under the License.

export default 100;
Copy link
Member

Choose a reason for hiding this comment

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

why is it better to have one constant per file rather than list them all in one file?

Copy link
Member Author

Choose a reason for hiding this comment

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

That's a valid point. I'll make the change.

@tiffon tiffon merged commit c15a3a2 into master Dec 19, 2017
@yurishkuro yurishkuro deleted the issue-130-config-for-dag-max branch January 29, 2020 15:06
vvvprabhakar pushed a commit to vvvprabhakar/jaeger-ui that referenced this pull request Jul 5, 2021
…fig-for-dag-max

Add a config value for the DAG cutoff
Signed-off-by: vvvprabhakar <vvvprabhakar@gmail.com>
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.

None yet

2 participants