-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide a default behavior to return valid JSON on /api/rest/projects/{projectId}/commits/{commitId}/changes #4414
Comments
tested on d4df511 I'll take advantage of this opened issue to share to other strange behaviours of the API Infinite Loops
examples to reproduce:
[
{
"consumption": 0,
"powerStatus": "NONE",
"status": "ACTIVE",
"usage": "UNUSED",
"outgoingFlows": [],
"name": "NewSystem",
"elements": [
{
"consumption": 0,
"powerStatus": "NONE",
"status": "ACTIVE",
"usage": "UNUSED",
"outgoingFlows": [],
"name": "CompositeProcessor1",
"elements": [
{
"status": "ACTIVE",
"usage": "UNUSED",
"incomingFlows": [
{
"status": "ACTIVE",
"usage": "STANDARD",
"capacity": 6,
"load": 6,
"target": {
"status": "ACTIVE",
"usage": "UNUSED",
"incomingFlows": [
{
"status": "ACTIVE",
"usage": "STANDARD",
"capacity": 6,
"load": 6,
"target": {
"status": "ACTIVE",
"usage": "UNUSED",
"incomingFlows": [
{
"status": "ACTIVE",
"usage": "STANDARD",
"capacity": 6,
"load": 6,
"target": {
"status": "ACTIVE",
"usage": "UNUSED",
"incomingFlows": [
{
"status": "ACTIVE",
"usage": "STANDARD",
"capacity": 6,
"load": 6,
"target": {
... (goes on and on through target -> incomingFlows -> target) Unhandled exception
steps to reproduce:
Please let me know if these behaviours are expected, or if you want me to create separate issues 🙂 |
Hi @AxelRICHARD and @sbegaudeau , |
Yes, please open separate issues for each different point mentioned above in your second response. About the first issue, related to the payload attribute, I will provide a fix soon. Thank you, Regards |
Bug: #4414 Signed-off-by: Axel RICHARD <[email protected]>
Thanks a lot!
No worries, I totally understand 🙂 |
Screenshots
#4393 (comment)
https://jsonformatter.curiousconcept.com/#
Steps to reproduce
/api/rest/projects/{projectId}/commits/{commitId}/changes
see
Expected behavior
Return valid RFC 8259 JSON
For example when no payload is defined return:
Actual behavior
"payload"
key with no value associated:according to @AxelRICHARD :
The text was updated successfully, but these errors were encountered: