[
https://issues.apache.org/jira/browse/FLINK-38853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048721#comment-18048721
]
Matthias Pohl edited comment on FLINK-38853 at 1/2/26 11:06 AM:
----------------------------------------------------------------
This change should be preceded by a ML discussion on whether we want to align
the JSON field casing in the [Flink Coding
Guidelines|https://flink.apache.org/how-to-contribute/code-style-and-quality-formatting/]
(as mentioned in the referenced text above).
was (Author: mapohl):
This change should be preceded by a ML discussion on whether we want to align
the JSON field casing in the [Flink Coding
Guidelines|https://flink.apache.org/how-to-contribute/code-style-and-quality-formatting/].
> Umbrella: FLIP-XXX: Enhance the standardization of the REST API JSON schema
> ---------------------------------------------------------------------------
>
> Key: FLINK-38853
> URL: https://issues.apache.org/jira/browse/FLINK-38853
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Reporter: Yuepeng Pan
> Priority: Minor
> Fix For: 3.0.0
>
>
> As discussed in
> [https://lists.apache.org/thread/w3lrn399vfxy1hhpoc1jgtgqlnr3w1p4.]
> > the JSON formatting is not specified in the coding guidelines. That's why
> > it comes with no
> > surprise that these formatting inconsistencies exist. We would need to
> > start a discussion
> > on updating the Flink coding guidelines first. Only afterwards, we could
> > fix the formatting. > Such a change would need to be rolled out as part of
> > a major version (e.g. 3.0) only, though.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
