-
Notifications
You must be signed in to change notification settings - Fork 3
Fix record history export #4
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
Open
jasper-lyons
wants to merge
11
commits into
primeroIMS:master
Choose a base branch
from
jasper-lyons:fix-record-history-export
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 3 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
bb669d4
fix: always escape keys in exported objects
jasper-lyons 6948ca2
fix: escape escape character so that it's rendered
jasper-lyons 3a4745d
Merge branch 'primeroIMS:master' into fix-record-history-export
jasper-lyons 48bd31a
Forcing a light GC every 100 attachements imported
jasper-lyons 2a52f24
fix: nont string keys throwing errors
jasper-lyons dbb12cd
fix: convert array of hashes to array of pairs
jasper-lyons 06450c8
Fix filename issues when exporting attachements
jasper-lyons 845ce0a
refactor: use the procedurale approach, it's cleaner
jasper-lyons 1f2be59
fix: use much smaller batch sizes for attachment exports
jasper-lyons 1d13c35
fix: stop overiding default batch sizes
jasper-lyons 0dc0587
Merge branch 'reduce-attachment-memory-consumption' into fix-record-h…
jasper-lyons File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
If you receive an integer you will get an exception. so you can keep the validation and add your escape to those that are not valid:
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.
I wouldn't want to rely on any
valid_key?
method for this, everything we're being passed should be a valid key given that it comes from an existing rubykey: value
pair afaik.I would instead just coerce everything to string before applying the
.gsub
.