Skip to content
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

critical api fix: verNum should not be undefined #2278

Merged
merged 1 commit into from
Mar 23, 2024

Conversation

GottZ
Copy link
Contributor

@GottZ GottZ commented Mar 23, 2024

closes #2276

this breaks excalibrain and other plugins that use the api to compare versions.

for some strange reason, closures like that now run pre-constructor so verNum is not defined at that point in time.
must be related to a change in electron / v8 or how the plugin builds.

@blacksmithgu blacksmithgu merged commit b52a0c6 into blacksmithgu:master Mar 23, 2024
3 checks passed
@GottZ GottZ deleted the fix-version-check branch March 23, 2024 08:20
holroy added a commit to holroy/obsidian-dataview that referenced this pull request Mar 23, 2024
@holroy
Copy link
Contributor

holroy commented Mar 23, 2024

I actually worked a little on this thingy tonight, and when I'd found a solution I couldn't find the bug anymore since you guys had already fixed it. 🥲 I did push the changes to my local fork, which is shown above, and that wasn't really the plan, but github decided to link it, so there it is. It can be ignored, unless this bug resurfaces again on a later stage.

@blacksmithgu
Copy link
Owner

It's definitely very strange... I do wonder what changed to break this.

@GottZ
Copy link
Contributor Author

GottZ commented Mar 24, 2024

I'll continue talking about it in the linked issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

api.version.compare('>=', '0.5.31') no longer works
3 participants