-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/zapier project description #17
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some minor comments.
src/Kentico.Xperience.Zapier/Admin/UIPages/ZapierNewApiKeyPage.cs
Outdated
Show resolved
Hide resolved
Assuming this PR updates the repo to be fully supported (instead of a Lab, as mentioned in the docs Changelog), we'll also want to update the following |
I have made the required adjustments. |
src/Kentico.Xperience.Zapier/Admin/InfoModels/ApiKeyInfoProvider.cs
Outdated
Show resolved
Hide resolved
Was there any reason for Zapier to target .Net 8.0? XbK targets .Net 6 and we should ideally target all integrations to the same version so that customers are not forced to upgrade entire projects to .Net 8 because of them. xperience-by-kentico-zapier/src/Kentico.Xperience.Zapier/Kentico.Xperience.Zapier.csproj Line 4 in 6e0175c
|
@michalJakubis This comes from our announced .NET 6 support guidance
|
This version reflects changes required by Project description word document.
As well as new nuget, Zap CLI application has to be pushed and published for zapier review
There are breaking changes, as we need to follow best practices document. I think that is not going to be a problem as the old version is preview version.