You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This relationship has, is the need to set the PropertySource name attribute to set, For nacos data structure design, under the same namespace, because of the existence of the group, data - id is the same, the possible so we can not only distinguish, according to the configuration data - id do it according to the data - id + group, internal by calculating a NacosPropertySource unique id as the default value of the name attribute, so if there is a priority setting their own configuration, is the need to manually set the name attribute
when I modified key in dataid second_example.properties, property key will be refreshed ,which is totally against my priority rule second_example.properties should be after example.properties
priority between dataids in @NacosPropertySources
Type: bug report
Consider this scenario
Here is an example
property value changed no matter which dataid is modified , however my expectation is only property key in the top priority dataid takes effect
The text was updated successfully, but these errors were encountered: