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

fixing typo ISO8601 #1871

Closed

Conversation

eviau-artefactual
Copy link
Contributor

Linked to archivematica/Issues#348 for the 8061 -> 8601 typo.

I am not sure if there is a better way than to use a global variable in order to generalize the use_iso_8601 help text... Maybe we don't want to generalize it?

I don't mind making the individual changes if we decide this is the way to go.

@eviau-artefactual
Copy link
Contributor Author

I wanted to test rebuilding AM with the change included, but I failed at finding instructions on how to do this - following the hack instructions resulted in a No such file or directory for the dockerfile when running make build

Let me know if I need to do something?

@eviau-artefactual
Copy link
Contributor Author

Oh my bad - I was in the wrong repo for Archivematica on my computer. make build seems to be working now.

sevein and others added 9 commits November 16, 2023 10:34
Only the first item in the `chain_choices` and `replacements` arrays was being
validated due to our usage of an array of schemas, leading to tuple validation.
In this context, each position in the array was expected to validate against
the schema at the corresponding position in the `items` array, leaving
subsequent items unvalidated.

This commit addresses this by converting `items` into a single schema object,
ensuring that validation applies to all items within the array, not just the
first.
This commit updates the workflow schema to no longer accept null values.
Previously required fields that permitted nulls have been modified to become
non-required.

Excluding null as an acceptable value is a backward-incompatible change.
However, as we have not committed to maintain backward compatibility,
implementing this change is acceptable.
* Remove language version settings in pre-commit config
* Remove flake8-import-order tox setting
* Update tox configuration
* Add flake8-bugbear
* Add flake8-comprehensions
* Add make rules to manage AMAUATs Python deps
* Update submodules
* Update GitHub CI workflows
* Upgrade pre-commit dependencies
* Remove vcrpy
This fixes the `List Unapproved Transfers` and `List SIPS Waiting for
User Input` API endpoints that were left behind after introducing the
Django 3.2 `UUIDField`.
@eviau-artefactual
Copy link
Contributor Author

Closing in favor of #1872

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants