add vscode pytest settings #19
Closed
Conversation
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
* chore: Remove is_valid checks from get_object_tags * fix: Rename ObjectTag perms to match model name * feat: Implement ObjectTag retrieve REST API Retrieve ObjectTags for given Object IDs, and optionally filter by taxonomy. * chore: bumped version
…ments team in weekly maintenance PRs
…thedocs fix: readthedocs file renamed
* feat: Remove object_tag_class from Taxonomy * feat: set tags by value, not tag_ref. Remove ObjectTag from Taxonomy. * chore: updated tests for system defined taxonomies * feat: more cleanups and validation for ObjectTag * feat: Remove "re-sync" of deleted taxonomies, update test_api.py * fix: case-insensitive values on MySQL * feat: minor cleanups * fix: fix flaky test * docs: Update system defined taxonomy creation ADR * chore: version bump: 0.2.0
…uirements-69519f4 Python Requirements Update, Fixing test cases
…uirements-0c4ca76 Python Requirements Update
chore: adds missing __init__.py files and fixes resulting pylint issues * fixes a number of translation-of-non-string * fixes coverage for files in tests/ * fixes PytestCollectionWarnings
feat: adds view to download CSV and JSON taxonomy import template files to demonstrate their format and usage. Also alters the import code to ignore extra fields in import files. This allows us to add comments to our template import files, but more importantly, allows users to import tags from an external source which may have extra data we don't care about.
…uirements-909e3f8 Python Requirements Update
* Authentication classes added to tagging API views * Cast taxonomies before serialize in TaxonomySerializer * Test updated
…quirements-ca6bc85 Python Requirements Update
…-requirements-c24a8e1 chore: Upgrade Python requirements
…-requirements-30e781f chore: Upgrade Python requirements
* ObjectTag.name is no longer a field, using export_id instead * KeyError: 'pk' * chore: bumps package version * fix: swagger docs missing queryset issue --------- Co-authored-by: Navin Karkera <navin@opencraft.com>
…-requirements-1223060 chore: Upgrade Python requirements
…x#276) * feat: adds unmark_copied_tags method to tagging API * chore: bumps package version
…-requirements-af6121a chore: Upgrade Python requirements
…-requirements-3416071 chore: Upgrade Python requirements
* feat: implement sketch of models and API for containers * feat: Implement higher-level APIs for getting components from units * feat: Expand tests cases, add more high-level APIs * refactor: Simplify EntityList: merge draft_version+published_version -> entity_version * refactor: Simplify create_next_unit_version() API * docs: mark all containers APIs as unstable * refactor: re-enable the too-many-positional-arguments pylint check * refactor: consolidate defined_list/initial_list/frozen_list into entity_list * test: add tests that publishes cascade down but not up * feat: get_containers_with_entity() API to find containers using a component * refactor: remove redundant 'entity' arg * feat: allow changing container title/metadata without changing its list * test: add test for deleting unit without affecting components within * refactor: ContainerEntity -> Container, ContainerEntityVersion -> ContainerVersion * fix: preloading with get_unit() was too minimal * test: update test_units_containing to catch bad JOINs in the query * refactor: move 'containers' models into publishing * feat: auto-publish children when publishing a container * feat: allow specifying components when creating a unit * refactor: Units inherit Containers (Multi-Table Inheritance) * feat: consolidate get_enitities_in_[published|draft]_container APIs * fix: ensure order_num is unique on each entity list row * refactor: move mixins to publishable_entity.py to avoid circular imports * feat: change get_components_in_unit() to raise if no published version * chore: version bump to 0.19.0 --------- Co-authored-by: Maria Grimaldi <maria.grimaldi@edunext.co> Co-authored-by: David Ormsbee <dave@axim.org>
…-requirements-0f63879 chore: Upgrade Python requirements
…dx#289) feat: add can_stand_alone flag to publishable entity It allows us to track components that were created independently and components that were created under a container like unit or subsection.
…PI [FC-0083] (openedx#287) * feat: adds get_containers and get_container_by_key to authoring api * test: improve test coverage of units api * chore: bumps package version
This will allow developers using VS Code to automatically detect, run, and deubg their tests using VS Code's Testing bar. To do this, we're explicitly passing --ds=test_settings to point pytest-django at the correct settings. Note that creating a pytest.ini file and adding DJANGO_SETTINGS_MODULE to it won't work for most developers who will be running these tests under Tutor. That's because Tutor will set the environment variable DJANGO_SETTINGS_MODULE for LMS or Studio (CMS), and this takes precedence over pytest.ini. This commit also starts a pattern for allow-listing specific configuration files in the .vscode directory. This is going to be a balancing act where we want to add just a few things that should be universally shared for convenience, like how to run tests or attach debugging to a running process. While VS Code does store user-specific settings elsewhere, individual developers may be running many plugins that put their own data in this directory.
Author
|
Sorry, this was absolutely a worked PR on my part. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
19 participants
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.
No description provided.