-
Notifications
You must be signed in to change notification settings - Fork 0
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
API redesign #248
Closed
2 of 19 tasks
Labels
type::quality assurance
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
Milestone
Comments
jon-nfc
added
the
type::quality assurance
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
label
Aug 19, 2024
jon-nfc
added a commit
that referenced
this issue
Aug 26, 2024
jon-nfc
added a commit
that referenced
this issue
Aug 26, 2024
jon-nfc
added a commit
that referenced
this issue
Aug 26, 2024
jon-nfc
added a commit
that referenced
this issue
Aug 26, 2024
This was referenced Sep 27, 2024
Open
Closed
jon-nfc
added a commit
to nofusscomputing/centurion_erp_ui
that referenced
this issue
Sep 27, 2024
This was referenced Sep 27, 2024
Closed
jon-nfc
added a commit
to nofusscomputing/centurion_erp_ui
that referenced
this issue
Sep 28, 2024
jon-nfc
added a commit
to nofusscomputing/centurion_erp_ui
that referenced
this issue
Sep 28, 2024
jon-nfc
added a commit
to nofusscomputing/centurion_erp_ui
that referenced
this issue
Sep 28, 2024
jon-nfc
added a commit
to nofusscomputing/centurion_erp_ui
that referenced
this issue
Sep 28, 2024
jon-nfc
added a commit
to nofusscomputing/centurion_erp_ui
that referenced
this issue
Sep 28, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 27, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 28, 2024
jon-nfc
added a commit
that referenced
this issue
Nov 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
type::quality assurance
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
API has no real structure, redesign so that ui can be separated.
Details
Down the track the UI will be separated from the API. For this to occur, the API needs to be suitable.
Models
__str__
function that will be used by serializer as fielddisplay_name
table_fields
Layout
Each model, not including tickets will be required to define its layout. this will be used by the UI to build the page layout for the model.
UI layout types are:
Detail layout is a primary models page. This lay displays all information pertinent to the model. This is inclusive of child models and linked items.
List layout is used as the landing page for models. it's a essentially a table view of all items the user has access to.
Settings layout is for models that are considered settings for other models. i.e. category field.
Ticket layout is for all models that have model ticket. this is regardless of the actual ticket type. The UI will distinguish between the different types.
Table Fields
Used to render the model in a table. All Models are required to specify this field.
Serializers
Serializes to be separated into three types:
Base Serializer
provides the basic details to show in place for a related model. To contains id, display_name and url.
Model Serializer
user for the creation and update of an item and contains ALL fields defined in display order, including any additional fields as specified within the View Serializer. these additional fields must be set as
read_only=True
Display Serializer
Used to serializer to display the data. related fields are redefined to use their own base serializer.
defines parameter
_urls: dict
that always contains key_self
which is the items detail view url.Views
Requirements
Links
Blocks: chore: initial work centurion_erp_ui#1
Related: API Browser #58
Related: AWX Browser #59
Related: Github API Browser #129
Related: Gitlab API Browser #128
Related: OSV API browser #130
Related: PyPi API Browser #132
Related UI Migration #307
Related: Team Users API Endpoint requires refactoring #351
Tasks
UI Proof of concept #319
chore: initial work centurion_erp_ui#1
Depreciate ALL API v1 endpoints
plan redesign
Work created from feat(core): ticket model #252
unit test
/api/core/tickets
unit test
/api/core/tickets/*/comments
unit test
/api/core/tickets/*/comments/*
ensure only
import
user can set the following ticket fieldsRequirements
Potential new issues
The text was updated successfully, but these errors were encountered: