-
Notifications
You must be signed in to change notification settings - Fork 36
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
apps folder must not become legacy behaviour #1408
Comments
We decided to rename the directory when we looked at allowing apps to be separate from the SDK. It was done so we could be 100% sure that the directory was for brjs apps and not another directory that happened to be called Now we're made a change to default to the working dir as the apps location (#1386) we probably don't need this @dchambers @ioanalianabalas thoughts? |
@andyberry88, if you are sure this is no longer necessary than of course it would be much better to only have one location rather than two, and given that we've only started using this new location in a release-candidate than I'm happy to just stop supporting |
I think that given we are currently using the working directory, we could make that change, definitely. Will we now be checking the existence of an
|
I'd suggest we do the following:
The change would be to remove the additional check for |
Sounds good 👍, @ioanalianabalas are you happy with this? |
Yes, should work fine 👍 |
I will start working on the modifications of this one, as #1414 depends on these changes. |
Fixed by #1417. |
👍 looks good |
I'm test upgrading our app to CT that uses BRJS RC1.
I get this warning in the console:
First issue is that the paths reported are wrong. Both folders are in the root of the repository, not in the SDK folder.
The second issue is that making
apps
legacy is unacceptable. We will not move our apps to a different folder as that will cause all sort of different problems.The text was updated successfully, but these errors were encountered: