Please add user: User as an argument, we don't want this to be un-authenticated

Originally posted by @ShubhranshuSanjeev in #17 (comment)

Current State

When an experiment is created from UI (and no operator is picked in context) - the operator defaults to has - we might need to default to is - we should force them to select one here. Additionally a context with has operator and is operator isn’t being merged

Add a delete button for each default config row in the table

Improve form inputs as per the types. Just for the primitive types.

• Add padding to the textareas, and some consistent min-height
• Text overflows in Context cards for big conditions (check mjos or sdkunified tenants)
• Context cards take full width of the content on Resolve page, resulting in horizontal scroll, should only span for the width of the screen with content-wrapping
• Use of null at someplaces in UI, to represent an unavailable value
  • Function Detail Page
  • Default-Config and Dimensions table to represent function name

Remove None option in Add Function dropdown for default-config and dimensions form.

Add a UI shimmer while waiting for data for the page. Today we show some text

Enable grouping toggle in default configs does not persist and has to be re toggled every time

Validate context before creation/update in context-aware-config

Superposition should have some info boxes explaining concepts, for example:

• Updating the priority of a dimension does not re trigger the computation of context priority. That has to be done manually
• experiments traffic percentage is capped

These are some I can think off. We should do this for any update operation where people may assume that the update cascades automatically (maybe we should do that?)

--> crates/context_aware_config/src/db/models.rs:88:15 | 88 | pub tags: Option<Vec<String>>, | ^^^^^^ the traitFromSql<diesel::sql_types::Nullablediesel::sql_types::Text, Pg>is not implemented for*const str``

          The return type should have been `superposition::Result<Vec<PriorityRecomputeResponse>>`

Originally posted by @ShubhranshuSanjeev in #17 (comment)

Show the computed priority of a context along with its overrides in override screen and resolve screen. This helps users get an idea of why priority is used, needed and how it impacts contexts. If we can even show how the priority is computed visually, that's great.

Using monaco editor improve the editing experience of large JSON objects

Remove KMS encryption that we brought in from the juspay framework. We can write a more generic way to read secrets like passwords from env

Create a paginated context list end point for displaying full list of all context overrides. Config end point's response is going to grow and this causes issues while rendering for the first time

• Better form fields
  • enum → dropdown of valid options
  • boolean → dropdown with true and false options
  • number -> input field should be number type
  • between -> Input fields need to be re-designed to help the user enter values

eclint pre-commit hook is failing for yaml files containing array of objects

UI feedback for form submission (reported by Kartik)

• Submit button can show a loader
• Button should be disabled while the request is on-going

Check validate is not of function type error on creating new function

In the default config form, when we try to add a new entry to the allowed list of entries by expanding the text box, first submit click closes the text box and the second one proceeds to do the actual API call

Today, we are not able to identify or traceback which experiment created a specific context override. Need more info around this

• Write unit tests to validate utility functions in frontend and ensure correctness
• Write unhappy test cases for obvious scenarios where things can go wrong for all APIs in newman-cli (80 - 20 principle)

The documentation and setup guide need to be updated. It guide today forces you to use nix, which is not really necessary. We should clean up the documentation and make it more open source friendly

We use Map<String, Value> to store the keys value pair of override form which being a Binary tree has it stored in alphabetic order, change this to use a vec of tuples.

Make monaco a component to be used with different fields and forms

Merge experiment and cac schemas to reduce the number of connections made to the database. It also helps manage the database more easily

Consistency point:

• Merge strategy option

Add test for the client and new operators

We need to implement delete default config api

Service utils crate brings in a lot of functions which may or may not be used in the importing crate. Add feature flags to service_utils crate, merge it with superposition_types and remove db and aws folders, replacing them with diesel-multiconnection-manger

For HAS operator we need to parse the type of each element of the array
For BETWEEN improve parse the two fields separated by a comma

A full Nix build (via nix run github:srid/nixci build) fails, due to clippy warnings:

If clippy is not used, I'd get rid of this:

To reproduce,

❯ nix flake check
warning: unknown flake output 'haskellFlakeProjectModules'
error: builder for '/nix/store/8qc30sswzi47pagn915asnvdk9ri9j7p-superposition-clippy-0.0.1.drv' failed with exit code 101;
       last 10 log lines:
       >     |
       > 107 |                 s.to_string()
       >     |                  ^^^^^^^^^^^^ help: remove this
       >     |
       >     = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#to_string_in_format_args
       >     = note: `-D clippy::to-string-in-format-args` implied by `-D warnings`
       >     = help: to override `-D warnings` add `#[allow(clippy::to_string_in_format_args)]`
       >
       > error: could not compile `service_utils` (lib) due to 21 previous errors
       > error: could not compile `service_utils` (lib test) due to 21 previous errors
       For full logs, run 'nix log /nix/store/8qc30sswzi47pagn915asnvdk9ri9j7p-superposition-clippy-0.0.1.drv'.

• Refactor context handlers, with a focus on schema validation.
• Disable override creation with empty context and empty overrides.

Overrides page appears to be cached and needs to be force refreshed - need to fix the caching behaviour.

The goal is to reduce the number of envs and better manage them. This includes refactoring code that reads envs.
Some examples
* CAC_HOST → SUPERPOSITION_HOST
* ENABLE_TENANT_AND_SCOPE → ENABLE_MULTI_TENANCY
* CONTEXT_AWARE_CONFIG_VERSION → SUPERPOSITION_VERSION
* MJOS_ALLOWED_ORIGINS → ALLOWED_ORIGINS
* (Not sure about what to do with this, DATABASE_URL contains all the info
* DATABASE_URL
* DB_USER
* DB_HOST
* DB_NAME

bun install is faster than npm, but does not change any other behaviour. Its an easy win for faster setup