Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] feat: new generator for React-Native with expo #379

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

29Hido
Copy link
Contributor

@29Hido 29Hido commented Mar 15, 2024

[WIP] New generator for React-Native using Expo

This PR is WIP

Lifting of the react-native generator
Current version of expo generator was made in Javascript, this version is fully typed with Typescript

Added libraries

TODO

  • Add support for mercure (present in current generator)
  • Add confirm box for delete button (present in current generator)
  • Handle hydra:prefix (not present in current generator)
  • Handle entity relations (not present in current generator)
  • Fix fields generation bug when generated from api-platform demo (not present in current generator)

Visual preview

Preview are from a real device

image
image
image

@29Hido 29Hido force-pushed the feat/generator-expo-v2 branch 4 times, most recently from 26eda39 to 5edfa65 Compare March 15, 2024 15:08
@dunglas
Copy link
Member

dunglas commented Mar 15, 2024

Pretty cool! Thank you very much for working on this.

Regarding the stack, two questions:

  • Is it still worth it to use Redux? It isn't hype anymore and it introduces a lot of complexity. As it's a minimal template, I'm not sure it is necessary
  • Can we use TanStack Query instead for API queries? It is popular and provides nice features.

@29Hido
Copy link
Contributor Author

29Hido commented Mar 18, 2024

Pretty cool! Thank you very much for working on this.

Regarding the stack, two questions:

* Is it still worth it to use Redux? It isn't hype anymore and it introduces a lot of complexity. As it's a minimal template, I'm not sure it is necessary

* Can we use TanStack Query instead for API queries? It is popular and provides nice features.

Hello

Yes we could, I'll try the migration to see how it goes but it seems better indeed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants