GithubHelp home page GithubHelp logo

Comments (4)

parse-github-assistant avatar parse-github-assistant commented on June 7, 2024

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

from parse-server.

mtrezza avatar mtrezza commented on June 7, 2024

It's currently not possible to change the JS SDK that ships with each Parse Server release.

I would say for good reason! The JS SDK is being used as an internal part of Parse Server. We are testing and releasing with a specific JS SDK. If we allow this to be overridden, then we may need 2 compatibility tables for the JS SDK, one for client use, another one for internal use. Maintaining such a compatibility table would require immense CI efforts, as we'd need to start testing Parse Server against multiple JS SDK versions.

I believe an effort into #8787 makes more sense. Once Parse Server does not depend on the JS SDK anymore, and its only dependency arises from the use of Cloud Code, then I believe the introduction of an option to set a specific SDK version makes sense. Because then there doesn't have to be any compatibility match anymore between the server and use of the JS SDK for Cloud Code, it's more isolated like an adapter.

from parse-server.

dplewis avatar dplewis commented on June 7, 2024

This feature is mainly used for the JS SDK test suite internal use and experienced developers to used at their own risk in cloud code only and would not touch the rest of the code base. It wouldn't conflict with #8787 in the future as it is an optional feature.

I believe an effort into #8787 makes more sense

This would be awesome but Parse Server is so tightly coupled with the JS SDK outside of cloud code it's going to take a lot of work to get this done. Parse.Error alone is used everythere.

from parse-server.

mtrezza avatar mtrezza commented on June 7, 2024

experienced developers to used at their own risk in cloud code only

I agree, but in that case there is no application for production use. We'd need to add a big warning label to that option and discourage production use. For experimental use, an experienced developer can fork and modify as needed.

Parse.Error alone is used everythere.

We have parse-community/Parse-SDK-JS#1269 for this.

from parse-server.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.