superfell/json2apex issues and pull requests

#45 - https://json2apex.herokuapp.com/ is no longer available

Issue - State: open - Opened by ryansieve about 2 months ago - 1 comment

#45 - https://json2apex.herokuapp.com/ is no longer available

Issue - State: open - Opened by ryansieve about 2 months ago - 1 comment

#44 - Multiple Empty Arrays Data Type Issue

Issue - State: closed - Opened by sidm1983 over 1 year ago - 2 comments

#44 - Multiple Empty Arrays Data Type Issue

Issue - State: closed - Opened by sidm1983 over 1 year ago - 2 comments

#43 - Error with this JSON

Issue - State: open - Opened by mauriciomoita almost 2 years ago - 1 comment

#43 - Error with this JSON

Issue - State: open - Opened by mauriciomoita almost 2 years ago - 1 comment

#42 - Tool is exclusively creating explicit parse code

Issue - State: closed - Opened by agency73-shared about 2 years ago - 5 comments

#42 - Tool is exclusively creating explicit parse code

Issue - State: closed - Opened by agency73-shared about 2 years ago - 5 comments

#41 - Will the hosted version be affected by the end of the Heroku free tier?

Issue - State: open - Opened by alexed1 about 2 years ago - 1 comment

#41 - Will the hosted version be affected by the end of the Heroku free tier?

Issue - State: open - Opened by alexed1 about 2 years ago - 1 comment

#40 - Updates reserved keywords to latest specs, fixes typo

Pull Request - State: closed - Opened by brianmfear over 3 years ago - 1 comment

#40 - Updates reserved keywords to latest specs, fixes typo

Pull Request - State: closed - Opened by brianmfear over 3 years ago - 1 comment

#39 - Guide me to Run this on Local PC

Issue - State: closed - Opened by kairavi-baxi almost 4 years ago - 4 comments

#39 - Guide me to Run this on Local PC

Issue - State: closed - Opened by kairavi-baxi almost 4 years ago - 4 comments

#38 - Should Escape More names

Issue - State: open - Opened by KarlLivesey about 4 years ago

#38 - Should Escape More names

Issue - State: open - Opened by KarlLivesey about 4 years ago

#37 - The Heroku play 1.x build pack is deprecated

Issue - State: open - Opened by superfell almost 5 years ago - 1 comment

#37 - The Heroku play 1.x build pack is deprecated

Issue - State: open - Opened by superfell almost 5 years ago - 1 comment

#36 - deal with heroku cedar-14 EOL

Issue - State: closed - Opened by superfell almost 5 years ago - 1 comment

#36 - deal with heroku cedar-14 EOL

Issue - State: closed - Opened by superfell almost 5 years ago - 1 comment

#35 - (Issue 34) Replace hyphens with underscores in member and class names.

Pull Request - State: closed - Opened by josephbleau almost 5 years ago - 1 comment

#35 - (Issue 34) Replace hyphens with underscores in member and class names.

Pull Request - State: closed - Opened by josephbleau almost 5 years ago - 1 comment

#34 - JSON keys with DASH/Hyphen is not supported.

Issue - State: closed - Opened by yasarshaikh almost 5 years ago - 3 comments

#34 - JSON keys with DASH/Hyphen is not supported.

Issue - State: closed - Opened by yasarshaikh almost 5 years ago - 3 comments

#33 - Issue 32 (do not merge, full integration/regression tests pending)

Pull Request - State: open - Opened by josephbleau almost 5 years ago - 3 comments

#32 - If a field has an explicitly null value in the JSON it is deserialized to Object.class even if later in the JSON that same field is represented as a specific type.

Issue - State: open - Opened by josephbleau almost 5 years ago - 5 comments

#31 - InnerClasses/Arrays unconventionally named.

Issue - State: open - Opened by MartinSpamer almost 6 years ago

#30 - Under class same name has JSON field

Issue - State: closed - Opened by Wykett over 6 years ago - 1 comment

#29 - The user supplied outer class name isn't validated correctly

Issue - State: open - Opened by superfell over 6 years ago

#28 - Need a test suite and a set of json test cases to validate.

Issue - State: closed - Opened by superfell over 6 years ago - 1 comment

#27 - handling of primitive arrays is broken with explict parse

Issue - State: closed - Opened by superfell over 6 years ago - 1 comment

#26 - JSON Identifier with dot produces Apex Class that fails to Compile: developer.email

Issue - State: closed - Opened by bobbywhitesfdc over 6 years ago

#25 - JSON fields names with leading underscore won't compile

Issue - State: closed - Opened by bobbywhitesfdc almost 7 years ago - 2 comments

#24 - Constructor not defined: [Object].<Constructor>(System.JSONParser)

Issue - State: open - Opened by textual over 7 years ago - 4 comments

#23 - Type name already in use: JSON2Apex.JSON2Apex

Issue - State: closed - Opened by madhu-ra over 7 years ago - 7 comments

#22 - Loosely typed array

Issue - State: open - Opened by ziqul over 7 years ago

#21 - Parsing array of records

Issue - State: closed - Opened by bobbywhitesfdc over 7 years ago - 5 comments

#20 - Problems parsing objects beginning with underscores

Issue - State: closed - Opened by amazingjoe about 8 years ago - 1 comment

#19 - Missing key word: date

Issue - State: closed - Opened by nzidol about 9 years ago - 2 comments

#18 - Error Code Help!

Issue - State: closed - Opened by ericmontepanda about 9 years ago - 3 comments

#17 - auto switch to generated parser for json that needs it

Issue - State: closed - Opened by superfell about 9 years ago

#16 - Test code needs to be in a separate class

Issue - State: closed - Opened by superfell about 9 years ago - 1 comment

#15 - If explict parsing code is enabled, should rename vars that clash with keywords.

Issue - State: closed - Opened by superfell about 9 years ago - 1 comment

#14 - JSON element named 'protected' causes unexpected token: 'protected' in generated code

Issue - State: closed - Opened by adtennant over 10 years ago - 1 comment

#13 - JSON2APEX help

Issue - State: closed - Opened by Ramiya04 about 11 years ago - 1 comment

#12 - Update to Play 1.2.6

Pull Request - State: closed - Opened by metadaddy over 11 years ago - 1 comment

#11 - Handle nulls when parsing JSON

Pull Request - State: closed - Opened by metadaddy almost 13 years ago - 6 comments

#10 - null in the json causes an NPE

Issue - State: closed - Opened by superfell almost 13 years ago

#9 - Merge fields from objects in arrays rather than creating heterogeneous arrays, added template for generating explicit parse code

Pull Request - State: closed - Opened by metadaddy almost 13 years ago - 3 comments

#8 - Escape single quotes

Pull Request - State: closed - Opened by metadaddy almost 13 years ago - 1 comment

#7 - Handle backslashes in JSON data

Pull Request - State: closed - Opened by metadaddy almost 13 years ago - 1 comment

#6 - spot sub types

Issue - State: open - Opened by superfell about 13 years ago

#5 - should generate a serialize as well as the deserialize method.

Issue - State: open - Opened by superfell about 13 years ago

#4 - generated test method needs to assert more.

Issue - State: open - Opened by superfell about 13 years ago

#3 - need to spot & fix type name collisions

Issue - State: closed - Opened by superfell about 13 years ago

#2 - types names need to not use reserved words

Issue - State: closed - Opened by superfell about 13 years ago

#1 - large sample json causes error

Issue - State: closed - Opened by superfell about 13 years ago - 4 comments

GitHub / superfell/json2apex issues and pull requests