-
Notifications
You must be signed in to change notification settings - Fork 30.6k
Changes deployed on the web-server are not applied when the application’s entry point is located outside the lib folder. #175318
Copy link
Copy link
Closed
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listcustomer: crowdAffects or could affect many people, though not necessarily a specific customer.Affects or could affect many people, though not necessarily a specific customer.dependency: dartDart team may need to help usDart team may need to help usf: integration_testThe flutter/packages/integration_test pluginThe flutter/packages/integration_test pluginfound in release: 3.35Found to occur in 3.35Found to occur in 3.35found in release: 3.37Found to occur in 3.37Found to occur in 3.37fyi-toolFor the attention of Flutter Tool teamFor the attention of Flutter Tool teamhas reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onplatform-webWeb applications specificallyWeb applications specificallyt: hot reloadReloading code during "flutter run"Reloading code during "flutter run"team-webOwned by Web platform teamOwned by Web platform teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.triaged-webTriaged by Web platform teamTriaged by Web platform team
Description
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listcustomer: crowdAffects or could affect many people, though not necessarily a specific customer.Affects or could affect many people, though not necessarily a specific customer.dependency: dartDart team may need to help usDart team may need to help usf: integration_testThe flutter/packages/integration_test pluginThe flutter/packages/integration_test pluginfound in release: 3.35Found to occur in 3.35Found to occur in 3.35found in release: 3.37Found to occur in 3.37Found to occur in 3.37fyi-toolFor the attention of Flutter Tool teamFor the attention of Flutter Tool teamhas reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onplatform-webWeb applications specificallyWeb applications specificallyt: hot reloadReloading code during "flutter run"Reloading code during "flutter run"team-webOwned by Web platform teamOwned by Web platform teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.triaged-webTriaged by Web platform teamTriaged by Web platform team
Type
Fields
Give feedbackNo fields configured for issues without a type.
Steps to reproduce
flutter create web_server_issue --platforms=web)main.dartoutsidelibfolder (i.e. move it intointegration_testdirectory)flutter run -d web-server -t integration_test/main.darthttp://localhost:PORTmain.dartsave and hot restart or hot reload your running app (or both)Expected results
Applied changes should be visible in the app.
Actual results
Applied changes are not visible. If
main.dartis placed underlibdirectory then it works.Why do I need it?
I’m working on a solution in Patrol that would let me “hot-restart” my e2e test (both the application code and the test code) so I don’t have to build and deploy the application for every change (called Patrol develop mode). The entry point of my “test-mode application” is a file specifically tailored to the nature of e2e tests, which is why it makes little sense to place it anywhere other than the
integration_testfolder (certainly not inlib).Code sample
Code sample
Flutter Doctor output
Doctor output