This repository has been archived by the owner on Jan 10, 2024. It is now read-only.
Added DateTime data type support. #48
Open
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
RemoteTK didn't seem to support datetime fields. Part of supporting them is sending the datetime value in the right format, which this function does per the Apex docs.
DateTime data type was missing. Addition of formatDateTime in RemoteTK.component helps ensure proper format is passed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
RemoteTK didn't seem to support DateTime fields when passed in the remote actions (kept getting illegal assignment errors back). This should fix it. Also added a "formatDateTime" helper method to remotetk.Client to ensure the format is consistent with what DateTime.valueOf() is expecting in Apex.