Improve wording of parse_error exception #4037

Activity

1. nlohmann

   added

   documentation

   good first issue

   on May 20, 2023
2. haseeb-xd commented on May 20, 2023

   

   haseeb-xd

   on May 20, 2023

   Last edited by haseeb-xd

   More actions

   I would like to work on this, Can you please tell me where can I add new parse_error exception message.
   Thanks
3. nlohmann commented on May 20, 2023

   

   nlohmann

   on May 20, 2023

   OwnerAuthor

   More actions

   Please check the code where parse_error is thrown.
4. theevilone45 commented on Jun 13, 2023

   

   theevilone45

   on Jun 13, 2023

   Contributor

   More actions

   Hey @nlohmann, can I do it? 😊
5. nlohmann commented on Jun 13, 2023

   

   nlohmann

   on Jun 13, 2023

   OwnerAuthor

   More actions

   Hey @nlohmann, can I do it? 😊

   Sure!
6. CosmicPegasis

   added a commit that references this issue on Jul 17, 2023

   Add better end of input error message (nlohmann#4037)

   63152c5
7. st17931 commented on Jul 25, 2023

   

   st17931

   on Jul 25, 2023

   More actions

   Is it done ?? Or i can look into it? @nlohmann
8. nlohmann commented on Jul 25, 2023

   

   nlohmann

   on Jul 25, 2023

   OwnerAuthor

   More actions

   See #4073. It's not done yet.
9. colbychaskell commented on Oct 7, 2023

   

   colbychaskell

   on Oct 7, 2023

   Last edited by colbychaskell

   Contributor

   More actions

   Looks like the work on this fell through... I can work on this if needed.
10. nlohmann

    linked a pull request that will close this issueAdd more specific error message when attempting to parse empty input #4180on Oct 31, 2023
11. nlohmann

    added this to the Release 3.11.3 milestone on Oct 31, 2023
12. nlohmann

    closed this as completedin #4180on Oct 31, 2023