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

Bug: Cannot save when a column is called export #169

Closed
jerebtw opened this issue Mar 22, 2023 · 2 comments
Closed

Bug: Cannot save when a column is called export #169

jerebtw opened this issue Mar 22, 2023 · 2 comments

Comments

@jerebtw
Copy link

jerebtw commented Mar 22, 2023

In a collection there is a column named "export" and when I try to edit this row, the admin UI loads forever and gives the following error message:

Uncaught TypeError: d.export is not a function
    at A (index-08378882.js:138:1285)
    at HTMLFormElement.$ (index-08378882.js:138:728)
    at HTMLFormElement.<anonymous> (index-08378882.js:1:3299)
@ganigeorgiev ganigeorgiev transferred this issue from pocketbase/pocketbase Mar 22, 2023
@ganigeorgiev
Copy link
Member

ganigeorgiev commented Mar 22, 2023

Hm, this is oversight on my part and something similar could happen I guess with isNew, clone, load named fields because these are helpers available with each BaseModel.

Maybe the better approach would be to prefix the helpers with $ so that they don't conflict with the dynamic record fields.

I'll try to update them sometime later this week (and maybe define an alias getter to preserve the backward compatibility).

@ganigeorgiev
Copy link
Member

The fields in the SDK were aliased as part of the v0.13.0 release.

The error in the Admin UI will be fixed together with the upcoming PocketBase v0.14.0 release (most likely sometime next week).

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

No branches or pull requests

2 participants