Vermont capable#28
Merged
Merged
Conversation
Allows devs to use localstack as an S3 mock. https://github.com/localstack/localstack
Instead of trying to keep it as a separate dropdown in the profile? That no one will use?
BryceStevenWilley
force-pushed
the
vermont_capable
branch
2 times, most recently
from
November 18, 2025 18:44
440b4b7 to
fd45174
Compare
Deleted two duplicate tests at the top of `tests.py` that are also present in `test_smoke.py`.
BryceStevenWilley
force-pushed
the
vermont_capable
branch
from
November 18, 2025 19:49
fd45174 to
b79811d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Gets us able to actual file with different jurisdictions; there was a lot of hard coding and weird pieces around before; removed most of them, and refactored what I could.
The jurisdiction URLs are
/<jurisdiction>/option, etc. No leading splitter like/jurisdiction/illinois, etc. Might want to switch to that (though the user visible URLs are cleaner without).Did not split the URLs under
/api/, and just passed jurisdiction as a param. Easier IMO, as long as how they're passed is consistent (which is not the case yet, still working on that).Big caveat; there's one thing still hardcoded: the
jurisdiction_idfrom thecase_data. This session data is used in a ton of places, and it's not super clear what's happening with it. That will probably be my next big refactor.Still papercuts everywhere and not non-expert dev lookable (ranking in my mind is:
)