-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
Improve app paths #86
Comments
Going to play with something that utilizes |
Maybe it would also be nice to be able to define multiple included/excluded paths. |
dcramer
added a commit
that referenced
this issue
Jul 26, 2017
This uses the root of the directory which ensures things like routes and core versioned code are managed, but explicitly excludes vendor. Refs GH-86
dcramer
added a commit
that referenced
this issue
Jul 26, 2017
This uses the root of the directory which ensures things like routes and core versioned code are managed, but explicitly excludes vendor. Refs GH-86
dcramer
added a commit
that referenced
this issue
Jul 26, 2017
This uses the root of the directory which ensures things like routes and core versioned code are managed, but explicitly excludes vendor. Refs GH-86
dcramer
added a commit
that referenced
this issue
Jul 26, 2017
This uses the root of the directory which ensures things like routes and core versioned code are managed, but explicitly excludes vendor. Refs GH-86
Merged
What about Lumen? Here you have a pull request for Lumen #128 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure how best to approach this, but for example, 'routes' is outside of
app_path
, and so generating an error there results in a poor user experience. We could usebase_path
as the app root, but then it includes vendor, which is also a problem. This possibly needs upstream changes tosentry/sentry
to make this behavior better.The text was updated successfully, but these errors were encountered: