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

[Feature Request] Support ampx --output-version 1 #4834

Open
hangoocn opened this issue May 6, 2024 · 2 comments
Open

[Feature Request] Support ampx --output-version 1 #4834

hangoocn opened this issue May 6, 2024 · 2 comments
Assignees
Labels
core Issues related to the Amplify Core Plugin feature-parity A request for a feature that is fully or partially available on another platform (JS, iOS, Android) feature-request A request for a new feature or an enhancement to an existing API or category.

Comments

@hangoocn
Copy link

hangoocn commented May 6, 2024

Hi just a follow up to this issue where we are required to add --outputs-versioin 0 to the ampx command.

I have created another react app using latest gen2 with version 1 outputs, and want to share the backend with the flutter app. So it will make it easy when both are on version 1.

May I know when it will support version 1 or is there any suggestion how to make both react and flutter app share same backend in amplify gen 2? Thanks!

@Jordan-Nelson Jordan-Nelson added feature-request A request for a new feature or an enhancement to an existing API or category. core Issues related to the Amplify Core Plugin labels May 6, 2024
@Jordan-Nelson
Copy link
Contributor

Hello @hangoocn - Support for the new format is in progress. We will let you know when it is available.

@Jordan-Nelson Jordan-Nelson added the feature-parity A request for a feature that is fully or partially available on another platform (JS, iOS, Android) label May 6, 2024
@andrew-clark-dev
Copy link

Can I add to this. It would be nice if I could pass the json config directly to the Amplify.configure. i.e. drop the dart generation. The main reason for this for me right now is that the --outputs-format parameter is not available for 'ampx pipeline-deploy' , thus meaning you cannot currently use the amplify frontend deploy to deploy flutter frontends.
As a workaround I have written a service that creates a conform config from the version 0 json (it is very fragile).
So in general it would be great if with this update we could use the generated json as I see no need for the dart format option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Issues related to the Amplify Core Plugin feature-parity A request for a feature that is fully or partially available on another platform (JS, iOS, Android) feature-request A request for a new feature or an enhancement to an existing API or category.
Projects
None yet
Development

No branches or pull requests

4 participants