Giter Club home page Giter Club logo

datapack-json's People

Contributors

dependabot[bot] avatar renovate-bot avatar spgoding avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

datapack-json's Issues

Recipe type has no minecraft: prefix

The extension marks recipe types that do contain the minecraft: prefix as non valid and hints me that I should use one of the proper ones: smelting, smoking, blasting and campfire.

Strange too though, shapeless and shaped don't get hinted as well. I think something is off in the JSON schemas here.

No support for item tag in entity equipment predicate

{
    "condition": "minecraft:entity_properties",
    "predicate": {
        "equipment": {
            "mainhand": {
                "tag": "minecraft:logs"
            }
        }
    },
    "entity": "this"
}

Be aware the property value doesn't use the usual leading # for the tag.

The automated release is failing 🚨

🚨 The automated release from the released branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the released branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


package.json not found. A package.json is required to release with vsce.

Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the semantic-release-vsce plugin to add more helpful information.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

Failed to recognize the category of a JSON file

Description

When an advancement file is put under a directory like this: data/<namespace>/advancements/recipes/, it will be recognized as a recipe.

Diagnostic

The current extension uses following configuration to provide JSON validations:

"jsonValidation": [
    ...
    {
        "fileMatch": "data/*/advancements/*.json",
        "url": "./src/advancement.json"
    },
    ...
    {
        "fileMatch": "data/*/recipes/*.json",
        "url": "./src/recipe.json"
    },
    ...
]

The ideal solution is to use a glob pattern like data/*/advancements/**/*.json to match files. But unfortunately, the fileMatch doesn't support double asterisks (**) for recursion purposes, that said, * indicates recursions already.

I have no idea about how to fix this problem, so I just open an issue and hope someone to help me out :/

DHP does not fully support 1.14 and 1.15

recipe "type": "minecraft:stonecutting" is not supported
recipe "type": "minecraft:crafting_special_*" are not supported
"item": "minecraft:honey_block" is not supported

Missing parameter

There should be an equipment property in ./shared/predicate.json#/definitions/entity.

The automated release is failing 🚨

🚨 The automated release from the released branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the released branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.