cloudfoundry / cloudfoundry/cf-java-client

Json Parser is too strict

未关闭
#1,341 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

DO NOT MERGE waiting-for-user
主要语言
Java
星标
334
派生
319
PR 合并指标
30 天内没有已合并 PR

描述

The parser that handles the responses from the cloud foundry instance is very strict and aborts processing as soon as an unknown property is received or a type does not match. There is no easy way for applications using the cf-java-client to continue processing.
This becomes a problem if the versions of client and server do not match or if test coverage in the integration-tests does not point to the problem during development of a new version.

There should be some central switch to log and ignore problems during message parsing as far as possible. The switch would be helpfull during development, when client and server versions do not match.

There should be a configuration file to ignore only explicitly listed properties that are save to ignore, even in a productive environment.

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

未指定任何文件、测试或入口点。首先定位响应消息解析器及其现有配置路径,然后确定未知属性和类型不匹配的处理方式。完成后应包含一个集中式的记录并忽略选项,以及用于显式忽略属性的配置,并覆盖这两种行为。

由索引模型根据 Issue 内容生成。

评估

技术栈
java
领域
api
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
冷清
描述清晰度
需要澄清
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。