Skip to content

docs: document how to test diracx-charts changes#931

Open
chaen wants to merge 2 commits into
DIRACGrid:mainfrom
chaen:doc_test_diracx_branch
Open

docs: document how to test diracx-charts changes#931
chaen wants to merge 2 commits into
DIRACGrid:mainfrom
chaen:doc_test_diracx_branch

Conversation

@chaen
Copy link
Copy Markdown
Contributor

@chaen chaen commented Jun 4, 2026

No description provided.

Comment thread docs/dev/how-to/test-changes-in-diracx-charts.md
@chaen chaen force-pushed the doc_test_diracx_branch branch from 4dcad64 to 108e471 Compare June 4, 2026 16:43
Comment thread docs/dev/how-to/test-changes-in-diracx-charts.md Outdated
@@ -0,0 +1,26 @@
# Testing changes in diracx-charts
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
# Testing changes in diracx-charts
# Testing against changes in diracx-charts

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

BTW, this is valid also for diracx-web, no?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It's true but may be a bit less important than diracx as we rarely need to modify diracx-charts when modifying diracx-web (e.g. no DB to add to the charts)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I was more meaning that if you need to test diracx together with diracx-web is the same technique?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Indeed, but theoretically diracx-web should only be built on top of stable diracx endpoints. A developer that would want to introduce a new endpoint would first need to get it in diracx validated, merged and released before working on the diracx-web interface (may be this should be documented though).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Could you add that in a diracx-web doc ?

@chaen chaen force-pushed the doc_test_diracx_branch branch from 108e471 to 8e78084 Compare June 5, 2026 09:13
@chaen chaen force-pushed the doc_test_diracx_branch branch from 8e78084 to afb51c1 Compare June 5, 2026 09:20
@read-the-docs-community
Copy link
Copy Markdown

Documentation build overview

📚 diracx | 🛠️ Build #33004878 | 📁 Comparing afb51c1 against latest (2937c6c)

  🔍 Preview build  

151 files changed · + 1 added · ± 150 modified

+ Added

± Modified

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.

3 participants