Skip to content

Enforce naming conventions #671

Closed
@cdavernas

Description

@cdavernas

What would you like to be added:

Enforce naming conventions of most (if not all) components.

I propose that we enforce using snake and/or kebab cased names.

Why is this needed:

In the case of functionDefs of type expression, for example, not enforcing a naming convention makes expression parsing a huge mess.

Consider the following example:

functions:
  - name: Say Hello
    type: expression
    operation: 'Hello!'

Now to call the function in an expression as defined by the spec, you'd need to write something like:

. | . * { "greetings": "fn:Say Hello" }

... which is impossible to parse both properly and/or safely. We could of course mandate to put the function's name between parenthesis (ex: $fn:(Say Hello)), for example, but I think the easier and cleanier approach is to go with a naming convention

Metadata

Metadata

Assignees

Labels

area: specChanges in the Specificationchange: featureNew feature or request. Impacts in a minor version change

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions