domitnator / kentico-kontent-nuxt-module Goto Github PK

Hi there,

I was curious as to why you downgraded from kentico-cloud-delivery-typescript-sdk from 3.1.0 to 2.5.3. Could you let me know some more details?

I've made some significant changes to the build process, suppose this has to do with that?

Anyway, I'm working on refactoring pretty much the whole SDK and this might help me figure out what I did wrong. Thanks!

Latest version is 10.0.0.

Code:
computed: {
getContent() {
return this.$deliveryClient.items()
.type('homepage')
.get()
.subscribe(response => console.log('DeliveryClient Response', response));
}
},

TypeError
Cannot read property 'items' of undefined

Hi! We really like this module; thanks for creating it!

Found a problem when we switched our nuxt.config.js usePreviewMode to false, set enableSecureMode to true, and switched Kentico's secure access option on for the production delivery api. Our requests to the Delivery Api were failing with the usual message when the Authorization header isn't correct.

In module.js, there's a couple properties that don't match the current Kentico js SDK docs:
securedApiKey => secureApiKey
enableSecureMode => useSecureMode
useSecureMode is a property of the globalQueryConfig object in the Kentico docs.

Making those changes in our local module.js and making matching changes in nuxt.config.js resolved the problem for us.

Would you like me to open a PR with these changes (and the nuxt.config.js section of the Readme docs)?

Thanks again for your work on this!
David

MomentJS is used for timestamp comparison but this can also be done in vanilla es6/javascript.

I seems like the IDeliveryClient has changed quite a bit. As soon as I figure our how rich text resolvers can be added, I'll add it as a comment

🚨 The automated release from the master 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 master 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:

• Usage documentation
• Frequently Asked Questions
• Support channels

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 📦🚀

Due to the complete typescript refactor the cacheservice-tests are lost. The should be rewritten in typescript and should be added to the project again.

Type resolvers should be supported!

Version 11 has just been released. (https://www.npmjs.com/package/@kentico/kontent-delivery) The kentico-kontent-nuxt-module should be updated accordingly!

Brief description

From the 1st of February the /items endpoint is limited to 1000 (incl. linked items) as described in Kontent API changes.

After that date, queries resulting in more than 1K content items per language won't load more than that 1K items.

Additional context

In the SDK, there is a method for enumerating all items
that allows all contents items loading. To provide this functionality via this module, it is necessary to upgrade .NET SDK to version <=12.1.0

Server side calls are throwing an exception.

For example:

asyncData ({ app }) {
      app.$deliveryClient.items().type('page').get().toPromise().then((response) => { 
        return { list: response.items } 
      });
  },

is throwin an exception:

"XMLHttpRequest is not supported by your browser"

The kontent-nuxt3-module should be migrated into this repository, see: nuxt/modules#163

🚨 The automated release from the UpgradeToBeta6 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 UpgradeToBeta6 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:

• Usage documentation
• Frequently Asked Questions
• Support channels

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 📦🚀

kontent.ai split from Kentico and now the package has a new name.

npm WARN deprecated @kentico/[email protected]: Package has been renamed to @kontent-ai/delivery-sdk. Please update your code to use the latest version

Currently there are no types available for this nuxt wrapper. It would be awesome to have the wrapped kontent.ai sdk types available inside of nuxt as well :)

There's a tracking header called X-KC-SOURCE that you can add to your plugin. We'll be then able to measure the adoption of your plugin and send you statistics of API calls made through the plugin.

You can set the header via the Kentico Kontent Delivery SDK.

v5 JS SDK approach: kontent-ai/gatsby-packages@e3612ae

v6 JS SDK: https://github.com/Kentico/gatsby-source-kentico-cloud/blob/js-sdk-ugrade-v6/src/gatsby-node.js#L96 or https://github.com/Kentico/gatsby-source-kentico-cloud/blob/master/src/gatsby-node.js#L96

Hi @Domitnator !
We've just renamed Kentico Cloud to Kentico Kontent. We are in the process of renaming all SDKs and Sample apps. Please consider renaming your plugin (code: namespaces, classes; repo, wiki, GH topics, etc.) to Kentico Kontent.

Thanks!