-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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: Import data via CSV #2359
Closed
Closed
Conversation
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
Thanks for opening this pull request!
|
* adding internal class (e.g. `_User`) fails due to prefixed underscore ([parse-community#2036](parse-community#2036)) ([f80bd07](parse-community@f80bd07))
# [4.0.0-alpha.17](parse-community/parse-dashboard@4.0.0-alpha.16...4.0.0-alpha.17) (2022-02-23) ### Bug Fixes * security upgrade prismjs from 1.26.0 to 1.27.0 ([parse-community#2047](parse-community#2047)) ([3afb24e](parse-community@3afb24e))
Snyk has created this PR to upgrade @babel/runtime from 7.17.0 to 7.17.2. See this package in npm: https://www.npmjs.com/package/@babel/runtime See this project in Snyk: https://app.snyk.io/org/acinader/project/3e039b91-2450-4b56-8420-baf56cab388e?utm_source=github&utm_medium=referral&page=upgrade-pr
# [4.0.0-alpha.18](parse-community/parse-dashboard@4.0.0-alpha.17...4.0.0-alpha.18) (2022-03-02) ### Bug Fixes * upgrade @babel/runtime from 7.17.0 to 7.17.2 ([parse-community#2055](parse-community#2055)) ([93335e9](parse-community@93335e9))
Snyk has created this PR to upgrade express from 4.17.2 to 4.17.3. See this package in npm: https://www.npmjs.com/package/express See this project in Snyk: https://app.snyk.io/org/acinader/project/3e039b91-2450-4b56-8420-baf56cab388e?utm_source=github&utm_medium=referral&page=upgrade-pr Co-authored-by: Manuel <[email protected]>
# [4.0.0-alpha.19](parse-community/parse-dashboard@4.0.0-alpha.18...4.0.0-alpha.19) (2022-03-10) ### Bug Fixes * upgrade express from 4.17.2 to 4.17.3 ([parse-community#2058](parse-community#2058)) ([f8dc602](parse-community@f8dc602))
# [4.0.0-alpha.20](parse-community/parse-dashboard@4.0.0-alpha.19...4.0.0-alpha.20) (2022-03-16) ### Features * change string filter description ([parse-community#2059](parse-community#2059)) ([bb1e184](parse-community@bb1e184))
Snyk has created this PR to upgrade otpauth from 7.0.10 to 7.0.11. See this package in npm: https://www.npmjs.com/package/otpauth See this project in Snyk: https://app.snyk.io/org/acinader/project/3e039b91-2450-4b56-8420-baf56cab388e?utm_source=github&utm_medium=referral&page=upgrade-pr
# [4.0.0-alpha.21](parse-community/parse-dashboard@4.0.0-alpha.20...4.0.0-alpha.21) (2022-03-18) ### Bug Fixes * upgrade otpauth from 7.0.10 to 7.0.11 ([parse-community#2061](parse-community#2061)) ([c379306](parse-community@c379306))
* adding internal class (e.g. `_User`) fails due to prefixed underscore ([parse-community#2036](parse-community#2036)) ([f80bd07](parse-community@f80bd07))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New Pull Request Checklist
Issue Description
Currently, it's not possible to import data
Closes: #307
Approach
Adds ability to import data.
Limitations:
TODOs before merging