Replaced get_element with JSONPointere.jl package #25

[YongHee-Kim]

Hello! It's been four years since I've proposed #25

It caught my attention recently and I've updated JSONPointer.jl and decided to tackle this issue as well

This pull request does not applied JuliaFormatter, but my next pull request for resolving #37 did used formatter accordingly

[odow]

I understand your motivation for this. But I'm still not really sure that I want to add a third-party dependency to save 37 lines of code.

What are the benefits of using JSONPointer over the current implementation?

[YongHee-Kim]

I have given some thought and you are right there isn't much benefits it brings to the JSONSchma.jl by adding JSONPointer dependency at the moment

Only potential benefits I could think of is providing better information when a 'reference' is broken for example

using JSON 
using JSONSchema

data = """
{
  "fruits": [ "apple", "orange", "pear" ],
  "vegetables": [
    {
      "veggieName": "potato",
      "veggieLike": true
    },
    {
      "veggieName": "broccoli",
      "veggieLike": false
    }
  ],
  "ref": { "\$ref": "#/fruits/0"},
  "ref2": { "\$ref": "#/fruits/3"},
  "ref3": { "\$ref": "#/vegetables/0/veggieName"},
  "ref3": { "\$ref": "#/vegetables/1/veggieNam"}
}
""" 
JSONSchema.Schema(data)

Will fail because #/fruits/3 and #/vegetables/1/veggieNam is wrong

Current error messages are:

With a JSONPointer commit, it will be

Albeit, I understand your reluctance for adding a dependency. I'm okay if you decide not to merge this pull request 😸