Option to define possible values for custom footer type

[boobiq]

Hello,

first of all thanks for a very nice plugin and I'd like to ask if it's possible (if it makes sense for you) to add option to define values for custom footer type in conventionalcommit.json schema?

We are using something like Action: <value> where value is one of some predefined values.

I suppose I could create some simple plugin with my own provider (is there maybe some example or documentation about how to do it?) but was wondering if such thing could be builtin feature.

Thanks!

[lppedd]

It should be possible by extending the default tokens schema.

I'll take a look soon.

[lppedd]

is there maybe some example or documentation about how to do it?

For your use case this seems overkill btw.
Custom providers are good mostly when you need to compute values, maybe from expensive network calls as they don't block the UI thread.

[lppedd]

This is more complex than expected, in the sense that it uncovered a deeper issue: the org.json library does not preserve JSON keys order (well it's the spec, but there is no option for it), resulting in a mess when calling completion.

Thus I'm also replacing the JSON-related libraries now, will take a bit longer.

[boobiq]

Thanks for your time and effort!

I was just curious why can't it be defined similar to scopes?

    "action": {
      "description": "Some description",
      "options": {
        "close": {},
        "revert": {},
        "whatever": {}
      }
    },

[lppedd]

It can, but up until now I did not realize the JSON lib is NOT maintaining keys ordering as internally it uses a hash map, and not a linked hash map.

It's not noticeable with three keys, but it is with ten+.

[boobiq]

And JSON arrays can't be used? There would be no additional fields to each option possible of course but for our case it's more than enough :)

   "action": {
      "description": "Some description",
      "options": ["close", "revert", "whatever"]
    },

[lppedd]

Sure, but in this specific context they make the schema and the resulting JSON worse to write.

I also want to encode values as objects, so that additional properties are easy to add, and potentially read from extenders.

[boobiq]

Thanks, makes sense, it's not feature just for me :)

[lppedd]

It's not easy to go back once you commit something, that's mostly why I take a cautious approach.

[lppedd]

Could you try this version? You'll have to install it manually.
The IDE completion via the schema should point you to the correct JSON structure.

idea-conventional-commit-0.25.0.zip

[boobiq]

Completion doesn't seem to be updated somehow, it only suggests existing fields, I checked the structure in repo, is this correct?

    {
      "name": "Action",
      "description": "action description",
      "values": {
        "something": {
          "description": "some description"
        },
        "else": {
          "description": "whatever"
        }
      }
    },

But when I try to type anything in commit msg area, I get "Error reading custom defaults file: the file does not respect the JSON schema. Using built-in tokens instead".

[lppedd]

Completion doesn't seem to be updated somehow

If Action is your custom footer type, you need to use:

// conventionalcommit.json
{
  "types": {
    ...
  },
  "footerTypes": {
    "Action": {
      "description": "action description",
      "values": {
        "something": {
          "description": "Some description"
        },
        "else": {
          "description": "whatever"
        }
      }
    }
  }
}

Also note that manually specifying the schema is not necessary. The correct schema should be injected automatically.