editoast: add field weight to op

[younesschrifi]

Part of #9746

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.87%. Comparing base (938dd3d) to head (38bc9e4).
Report is 2 commits behind head on dev.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #9775      +/-   ##
==========================================
- Coverage   79.88%   79.87%   -0.02%     
==========================================
  Files        1048     1048              
  Lines      105242   105245       +3     
  Branches      756      756              
==========================================
- Hits        84073    84061      -12     
- Misses      21128    21143      +15     
  Partials       41       41              

Flag	Coverage Δ
editoast	73.41% <100.00%> (-0.05%)	⬇️
front	89.36% <ø> (ø)
gateway	2.18% <ø> (ø)
osrdyne	3.28% <ø> (ø)
railjson_generator	87.50% <100.00%> (+0.01%)	⬆️
tests	87.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[shenriotpro]

LGTM for tests/

[Erashin]

Is the PR title fine? Not used to see this format.
Core lgtm otherwise.

[Maymanaf]

LGTM for e2e tests
You just need to wait for this PR to be merged before

[flomonster]

LGTM

[Khoyo]

Is the PR title fine? Not used to see this format.

The default title for multi-commit pr is the name of the branch (instead of the commit title). It's not an ideal title but they don't end up in the git history anyway as we do fast-forward merges only

[emersion]

They do end up in release notes though (and in general are not very readable).

[younesschrifi]

Thank you @emersion for your comment. I'll do better next time :)

[woshilapin]

I'm sorry, I removed this PR from the merge queue.

Sure, most commits are separated which helps for review, but this doesn't make for a reasonable atomic change. So before merging, I believe these should be squashed. For example, changing the schemas in osrd_schemas without changing the corresponding schemas in editoast in the same commit is a mistake to me. That's the reason why we do have a monorepo and change can be done everywhere in one operation. What do you think?

And yes, sure, the title of the PR is not kept around in the git repository, but it's still kept in the Github where all the other PR titles respects some kind of standard formatting. And they end up in the release.

I could also argue that the description of the PR doesn't really help understand the full context (it links to an issue where there is nothing but a title).

Most of the contributions guidelines are here. I know we not always follow them to the line, but here, there are multiple problems and I believe some of them should be addressed (PR title, PR description, non-atomic commits).