Recipes not using Create Namespace
See original GitHub issueIn reference to this issue, we have discovered that Create’s recipes are using the default minecraft
namespace, not the create
namespace. This can be seen here:
I’d be glad to make a PR if that would help – otherwise, this may cause unexpected behavior (which it already has, as you may see in the referred issue).
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Create a namespace - Akamai TechDocs
Creates a namespace on Akamai's STAGING or PRODUCTION network. You should create namespaces in both networks so that you can test your EdgeWorkers...
Read more >Best Practice Recipes for Publishing RDF Vocabularies - W3C
Abstract. This document describes best practice recipes for publishing an RDFS or OWL vocabulary or ontology on the Web.
Read more >chef reassigning attributes from another namespace in recipe ...
Because I have consul in server and client modes I want to separate namespaces. In this case, I can use following construction in...
Read more >Using namespaces | Clojure Programming Cookbook
This recipe does not require any special installation steps apart from a running REPL. ... We will go through the steps of creating...
Read more >Learn Kubernetes 101 - Part 1 - Using Namespaces
You can also create a namespace using a YAML file, which is a configuration file. You could create a YAML file from the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I would hazard a significant reminder/notice along with this though, sneaking it wouldn’t necessarily help as it will result in all recipes in datapacks being invalidated.
Hi, thanks for the report! That is an oversight indeed, I’ll sneak a fix into the next update, though I have no ETA for it as of yet. I hope using data packs for now will get you what you’re after =S