Giter Club home page Giter Club logo

Comments (6)

kastermester avatar kastermester commented on July 24, 2024 1

I just edited in my thoughts as you replied, realised it might not be obvious why it would be a good idea.

from relay-compiler-language-typescript.

kastermester avatar kastermester commented on July 24, 2024

I see now.

This does indeed seem quite weird. I think there's still value in emitting the types (just as flow does) but emit those as any as well (ie. not as a unique symbol type).

Ie. for the above linked playground we should emit something like this instead

EDIT:

The value we gain is that it allows people to use Relay with typescript without having to typecast to any when rendering the components, as the typings inside the react-relay package will now simply mark that the property value doesn't matter, but still transform the prop types.

from relay-compiler-language-typescript.

alloy avatar alloy commented on July 24, 2024

Fair, we could do that too. What’s your thought for there still being value? Just as a named label that could help indicate what reference is required?

from relay-compiler-language-typescript.

alloy avatar alloy commented on July 24, 2024

@ckknight Are you perchance interested in submitting a PR for that? The type generator receives a flag that indicates wether or not the single artefact directory feature is enabled.

Having said all that, and we absolutely should not break the default setup, I would suggest you consider enabling the single artefact directory feature after all, as it’s the only stable simple way we could come up with that would allow you to have typed fragment references without using the Haste module system.

from relay-compiler-language-typescript.

kastermester avatar kastermester commented on July 24, 2024

To be honest I would not be too surprised if using the single artifact directory ends out being the way most people will use relay going forward (either that or we get some nifty way of tracking where the artifacts are being output in the future such that we can get around the issues we're circumventing by using this feature). It helps both Flow and TypeScript users get the typechecking features they deserve.

With that said - making the changes stated here makes sense, it will help us reach parity with the Flow implementation.

from relay-compiler-language-typescript.

alloy avatar alloy commented on July 24, 2024

Agreed. facebook/relay#2509

from relay-compiler-language-typescript.

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.