最新版1.8.1 dashboard基于Nacos持久化XXXRule 和XXXEntity的问题
Open
area/dashboard
kind/question
- Dominant language
- Java
- Stars
- 23.1k
- Forks
- 8.1k
- PR merge metrics
- No merged PRs in 30d
Description
1.nacos以json的数据格式持久化,看nacos test的例子都是将XXXEntity的对象转换成json,但是直连客户端的源码其实是将XXXEntity转换成XXXRule的方法再发给客户端的,请问这2个对象会不会有哪里属性对不上,有没有踩过坑的朋友交流一下?
2.比较2个类,主要是Entity需要app ip port 3个参数,如果以XXXRule json格式持久化,改动的地方比较多,代码不好组织,有没有人有成熟例子可以分享下?
3.这2个类是不是可以做到统一?
Contributor guide
Research direction
Compare the Nacos test examples that persist XXXEntity as JSON with the direct-client source that converts XXXEntity to XXXRule. First identify mismatched properties and the app, IP, and port parameters; done would require a decided persistence approach or a documented way to unify the two classes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100