EnchantmentHandler?

[UnintelligentIdiot]

This will be nice

[WFPhantom]

No idea how I missed that one, good idea!

Something like this as the structure perhaps

"modifiers":{
    "enchantment": [
        { "minecraft:sharpness": 5 }
    ]
}

or maybe handle it outside of modifiers?

"modifiers":{},
"enchantments":{
    "minecraft:sharpness: 5
}

will look into it for 1.2, thanks for the suggestion

[UnintelligentIdiot]

do it like minecraft does

"enchantments":[
{"minecraft:sharpness": 5},
{"minecraft:silk_touch"} #{"minecraft:silk_touch": 1}
]

or even better

"components":[
"enchantments":[
{"minecraft:sharpness": 5},
{"minecraft:silk_touch"} #{"minecraft:silk_touch": 1}
],
....
]

since the files are already in modify folder there is no need for you to specify

[WFPhantom]

I think even enchantments capped to 1 like silk_touch and infinity should have a number mapped to them like

"minecraft:silk_touch": 1,
"minecraft:infinity": 1

just in case some mod decides do change those values for god knows what reason.

As for the structure, is there any benefit to adding the unnecessary complexity of it being an array or having a components wrapper? I don't see a reason to deliberately add the complexity of minecraft's component format if i can just pass a list of enchantments in datagear's format as simple as

"enchantments":{
    "minecraft:sharpness": 5,
    "minecraft:silk_touch": 1
}

[UnintelligentIdiot]

Having the components wrapper instead of modiers is simply easier to understand. You are already specifying that is modifying with the structure folder of data/<namespace>/datagear/_modify_/<file>.json and its more logical to have components since the whole json is modifying the items
as for the complexity of the format you can simplify it, it will just look better
You should see what components minecraft already has to offer and the rest who are not there you can just add it your self

The enchantments being capped at 1 is a good thing

[WFPhantom]

Oh you mean rename modifiers to components? I agree with that. Like this?

{
    "target": "minecraft:diamond_sword",
    "operation": "add",
    "components": {
        "attack_damage": 3.0,
        "unbreakable": true
    },
    "enchantments": {
        "minecraft:sharpness": 5
    }
}

You should see what components minecraft already has to offer and the rest who are not there you can just add it your self

Datagear mostly dynamically searches for components, that way i do not have to do any compat with mods, they automatically get assigned to a type without me having to add them

The enchantments being capped at 1 is a good thing

I agree, but json doesn't support keys without values, and it is not in-scope of datagear to be limiting enchantment levels

[UnintelligentIdiot]

So wouldn't it be better to just add ComponentHandler? This is the same thing that a recipe can do and a loot table

{
  "type": "minecraft:crafting_shapeless",
  "ingredients": [
    [
      "minecraft:debug_stick"
    ]
  ],
  "result": {
    "id": "minecraft:golden_axe",
    "components": {
      "minecraft:item_name": "Rose Gold Axe",
      "minecraft:lore": [
        "Better then Gold Axe",
        "",
        ""
      ],
      "minecraft:max_damage": 700,
      "minecraft:attribute_modifiers": [
        {
          "type": "minecraft:attack_damage",
          "amount": 80,
          "operation": "add_value"
        }
      ],
      "minecraft:stored_enchantments": {
        "minecraft:silk_touch": 1
      },
      "minecraft:repair_cost": 0
    }
  }
}