AbsaOSS / AbsaOSS/enceladus

Make sure the Menas uses only one source of project version information

未關閉
#1,564 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
Menas priority: low refactoring UX
主要語言
Scala
星號
33
分支
16
PR 合併指標
30 天內沒有已合併 PR

描述

## Background
Project version used in Spring (Menas UI) in different parts of code can theoretically diverge, which would break the UI

## Feature
`"/${enceladusVersion()}/**"` is supposed to be a root path to our sources. Which is set using `spring.resources.chain.strategy.fixed.version` from app properties. But here we "enable" it using `ProjectMetadata.enceladusVersion`. And in some other places of our project (`index.html`), we again use `ProjectMetadata.enceladusVersion`. If these two versions ever become different, Menas becomes unusable.

貢獻指南

開啟貢獻指南

研究方向

Trace the uses of ProjectMetadata.enceladusVersion, enceladusVersion(), spring.resources.chain.strategy.fixed.version, and the version reference in index.html. Determine where the project version is defined and how the Spring resource path and Menas UI consume it. Done means these consumers use one consistent source so the UI cannot break when versions diverge.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
scala, spring
領域
full-stack
Issue 類型
重構
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
需要釐清
新手友好度
35/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。