You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Setting the api to "6.0" makes the plugin not work for Cura 3.6. See this thread about making plugins that are compatible with multiple Cura versions: Ultimaker/Uranium#460 (comment)
Also note that the "minimum_cura_version" and "maximum_cura_version" are not used by Cura. They have no meaning, unless the plugin itself looks at these keys. I added them to some of my plugins as a meassure to make sure my plugins don't blow up Cura when used with untested versions of Cura. See https://github.com/fieldOfView/Cura-OctoPrintPlugin/blob/3.5/__init__.py#L31
The reason will be displayed to describe this comment to others. Learn more.
About the API version: I thought the Marketplace re-generates the plugin.json file anyway and substitutes the correct one? So currently only people that want to install from my git-source might have problems...
About the cura-version: thanks - I can probably get rid of them. I'm not using them anywhere.
2038382
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.
Setting the api to "6.0" makes the plugin not work for Cura 3.6. See this thread about making plugins that are compatible with multiple Cura versions:
Ultimaker/Uranium#460 (comment)
Also note that the "minimum_cura_version" and "maximum_cura_version" are not used by Cura. They have no meaning, unless the plugin itself looks at these keys. I added them to some of my plugins as a meassure to make sure my plugins don't blow up Cura when used with untested versions of Cura. See https://github.com/fieldOfView/Cura-OctoPrintPlugin/blob/3.5/__init__.py#L31
2038382
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.
About the API version: I thought the Marketplace re-generates the plugin.json file anyway and substitutes the correct one? So currently only people that want to install from my git-source might have problems...
About the cura-version: thanks - I can probably get rid of them. I'm not using them anywhere.
2038382
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.
Nevermind - I actually had some changes already lined up, but not pushed yet.
Would you mind checking with latest master again?
Thanks for the feedback!
2038382
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.
The marketplace backend does not touch your plugin.json, but adds a package.json
2038382
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.
Looks better now. The reason I looked into your repo was this issue: Ultimaker/Cura#5262, not sure if you had seen it.
2038382
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.
Thanks - no I haven't seen that issue. I'll test and comment there.